[Dspace-devel] Start- and EndDates for Permissions
Hi, I'm currently working on DS-1965 (https://jira.duraspace.org/browse/DS-1965). It targets the issue that the start and end date of a ResourcePolicy can't be changed/set/removed in the administration interface of the JSPUI. This is problematic if you use Embargo in JSPUI. While it is quite easy to resolve this problem I have two questions regarding the policy dates in DSpace: 1) In DSpace 3.0 the advanced Embargo was introduced and the way Embargos are implemented in DSpace changed. Before 3.0 we had an embargo lifter and Embargo end dates. 3.0 introduced start Dates for permissions, so that Resource Policies don't have to be changed by an embargo lifter anymore. Is there a reason why we still support End Dates for Resource Policies? 2) Is it correct, that DSpace uses start (and perhaps end dates) for resource policies only for Items and Bitstreams? Do we support using dates for ResourcePolicies on Bundles, Communities and/or Collections? I would appreciate any answer especially how this is handled in XMLUI so we can get a common behavior in both UIs. Thanks in advance, Pascal -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Understanding build failure for a PR
The travis build for my PR failed at a spot unrelated to my code changes. https://github.com/DSpace/DSpace/pull/916 Could you offer any advice? Here is the error: Results : Failed tests: InstallItemTest.testInstallItem_todayAsIssuedDate:207 testInstallItem_todayAsIssuedDate 0 Expected: 2015-04-14 but: was 2015-04-15 InstallItemTest.testRestoreItem_todayAsIssuedDate:259 testRestoreItem_todayAsIssuedDate 0 Expected: 2015-04-14 but: was 2015-04-15 Tests run: 636, Failures: 2, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] DSpace Parent Project .. SUCCESS [ 18.653 s] [INFO] DSpace Services Framework :: API and Implementation SUCCESS [ 19.178 s] [INFO] DSpace Kernel :: API and Implementation FAILURE [01:45 min] Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://www.library.georgetown.edu/lit/code 425-298-5498 (Seattle, WA) -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Understanding build failure for a PR
This wouldn't be some silly thing like, the travis run started before midnight and ended after, right? Just noting that the dates are yesterday/today and your e-mail Terry was sent close to midnight UTC. cheers, Andrea On 15/04/15 11:45, Terry Brady wrote: The travis build for my PR failed at a spot unrelated to my code changes. https://github.com/DSpace/DSpace/pull/916 Could you offer any advice? Here is the error: Results :Failed tests: InstallItemTest.testInstallItem_todayAsIssuedDate:207 testInstallItem_todayAsIssuedDate 0Expected: "2015-04-14" but: was "2015-04-15" < /span> InstallItemTest.testRestoreItem_todayAsIssuedDate:259 testRestoreItem_todayAsIssuedDate 0Expected: "2015-04-14" but: was "2015-04-15"Tests run: 636, Failures: 2, Errors: 0, Skipped: 0[INFO] [INFO] Reactor Summary:[INFO] [INFO] DSpace Parent Project .. SUCCESS [ 18.653 s][INFO] DSpace Services Framework :: API and Implementation SUCCESS [ 19.178 s][INFO] DSpace Kernel :: API and Implementation FAILURE [01:45 min] Thanks, Terry -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://www.library.georgetown.edu/lit/code 425-298-5498 (Seattle, WA) -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Dr Andrea Schweer IRR Technical Specialist, ITS Information Systems The University of Waikato, Hamilton, New Zealand -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] DSpace Dev Mtg Tomorrow @ 20:00 UTC and JIRA Backlog Hour @ 19:00 UTC
All, Tomorrow (Weds, April 15) at 20:00 UTC, we have our weekly DSpace Developers Meeting in the #duraspace IRC channel. To determine your local time, check the world clock: http://www.timeanddate.com/worldclock/fixedtime.html?hour=20min=0sec=0p1=0 The agenda is posted on our Developer meetings page at: https://wiki.duraspace.org/display/DSPACE/Developer+Meetings The notes from last week's meeting are also available off of the Meeting Archives area of that page. As always, all our meetings are public. We welcome any developers or non-developers to attend or just read along with the chat discussions. If you are unable to attend, you can always add your own notes/thoughts on any agenda item to the above wiki page. == JIRA Backlog Hour == The hour prior to our Developers Meeting, we will be holding a JIRA Backlog Hour in #dspace IRC (note that it takes place in #dspace and NOT #duraspace). During this meeting, developers who are available will begin to work together to tackle our backlog of Received tickets/bug reports in JIRA. We'll be looking to do a quick analysis of tickets to help move them along through our workflow. Anyone is welcome to join us (and you are more than welcome to just join mid-meeting as well). It's a great way to learn about how we work together to support DSpace, and also a great way to contribute to DSpace software. Plus, you'll be helping all of us to determine which tickets (old and new) could use extra love attention. Our current JIRA Received backlog is at: https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+DS+AND+status+%3D+Received+ORDER+BY+key+ASC%2C+priority+DESC We hope to see you in IRC! Thanks, Tim Donohue Technical Lead for DSpace Project DuraSpace.org -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Start- and EndDates for Permissions
On Tue, Apr 14, 2015 at 11:02:12AM +, Becker, Pascal-Nicolas wrote: I'm currently working on DS-1965 (https://jira.duraspace.org/browse/DS-1965). It targets the issue that the start and end date of a ResourcePolicy can't be changed/set/removed in the administration interface of the JSPUI. This is problematic if you use Embargo in JSPUI. While it is quite easy to resolve this problem I have two questions regarding the policy dates in DSpace: 1) In DSpace 3.0 the advanced Embargo was introduced and the way Embargos are implemented in DSpace changed. Before 3.0 we had an embargo lifter and Embargo end dates. 3.0 introduced start Dates for permissions, so that Resource Policies don't have to be changed by an embargo lifter anymore. Is there a reason why we still support End Dates for Resource Policies? My reading of the current documentation (https://wiki.duraspace.org/display/DSDOC5x/Embargo#Embargo-Pre-DSpace3.0EmbargoCompatibility) suggests that Advanced Embargo did not replace the original scheme, but lives alongside it, probably to ease migration to the new method. Apparently the original embargo code has been extended to handle 'ResourcePolicy's but still uses its own fields. Perhaps it is time to deprecate the original embargo method and set a release for its removal? -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: Digital signature -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15utm_medium=emailutm_campaign=VA_SF___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
