Hi Tim, For us there a couple of reasons, one is that we’re on Dspace 3, where the default behavior (if I’m remembering correctly from when we upgraded) was to withdraw items with the private flag in the InstallItem class. In the future, we’ll likely just use the private flag to indicate a “dark” item.
The second reason for us to customize the embargo system is that our original system was an in-house embargo module for space 1.5 (I think the 1.6 plugin was somewhat based on ours, I’m talking about Ideals here so, Tim, you probably remember). We ended up cobbling together aspects of the 1.6 system and the 3.0 embargo system to more closely replicate the interface we had previously. Essentially, we needed to support a campus-only option that the simple embargo form didn’t have, but we didn’t want to retrain our users to use the Advanced embargo form. We also wanted to expand our embargo system to allow different embargoes to apply to individual bitstreams, so we opted not to just port our 1.5 system. Most of the logic is therefore controlled by resource policies on bitstreams, but since we’re still supporting high-level item-centric options, we needed to store that information in the metadata. Thanks, Seth On 4/21/15, 11:01 AM, "Tim Donohue" <[email protected]> wrote: >Hi helix84 & Seth, > >Just out of curiousity, is there a particular reason why you wouldn't >just use the "Access" Step instead of "hacking" the same thing via a >temporary withdrawal & reinstate? The "Access" step already lets you >specify that READ access wouldn't start until a particular date has >passed. But, maybe I'm missing something about your particular use case? > >https://wiki.duraspace.org/display/DSDOC5x/Embargo#Embargo-AccessStep > >As noted in my other response to this thread, this functionality seems >to already exist as part of the optional "Access" step (unless I'm >misunderstanding something here?) > >http://dspace.2283337.n4.nabble.com/Advanced-Embargo-Dark-Metadata-tp46774 >98p4677503.html > >- Tim > >On 4/21/2015 10:55 AM, helix84 wrote: >> On Tue, Apr 21, 2015 at 5:45 PM, Robbins, Seth David >> <[email protected] <mailto:[email protected]>> wrote: >> >> We do what Helix describes, but we¹re looking for another way. It's >> a hack >> to store information crucial to actionable business logic in the >> descriptive metadata. >> >> >> Depends on how you look at it - it is also a way to allow a wider group >> of users to easily edit the date - the 1.6 embargo does the same thing. >> >> But if you insist, it's not any harder to make the curation task look at >> resource policies instead of item metadata. You could use item resource >> policy or a resource policy of one of the bitstreams or one with a >> special name. Such implementation will still be contained within the >> curation task and doesn't require changes to DSpace. >> >> >> Regards, >> ~~helix84 >> >> Compulsory reading: DSpace Mailing List Etiquette >> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> >> >> >> >>------------------------------------------------------------------------- >>----- >> 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_15&utm_medium=email&utm_campaign=VA_SF >> >> >> >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> List Etiquette: >>https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> ------------------------------------------------------------------------------ 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_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
