Hi Stuart: I'll take a crack at some of your questions: see remarks inline below.
Thanks, Richard R On Tue, 2009-12-08 at 17:40 +1300, stuart yeates wrote: > I have some questions about the Embargo plugin in 1.6. I'm basing this > on http://wiki.dspace.org/index.php/Embargo_1.6 and trolling through the > subversion repository (dspace-1.6.0-rc1 tag). > > We'd like to have an drop-down box in our self-deposit which allows > users to select an embargo period (probably 3, 6, 12, 18 or 24 months). > This then gets put in the metadata field pointed to by > embargo.field.terms (probably 'VUW.embargo'), and the date of uplift > calculated and stored in that pointed to by embargo.field.lift (probably > 'available'). As far as submission goes, you could do this fairly easily by using the configurations available in 'input-forms.xml' by defining the drop-down list and it's values. See the doc for more information (all XML, no Java) > > The DefaultEmbargoSetter automatically sets the default permissions so > that while the item metadata for an embargoed item is globally readable, > the bitstreams are inaccessible to everyone but admins. [This could be > overridden to a less strict lockdown by overriding the setEmbargo > method, we havent' thrashed this out yet] DefaultEmbargoSetter also > calculates the embargo.field.lift date, from the embargo.field.terms and > the current time/date. > > Once a day the EmbargoManager runs and uplifts items whose embargo has > expired. Uplifting involves setting the permissions to whatever the > default permissions are for the collection it's in, making item's > bitstreams public. > > My questions are: > [1] Does the above sound sane? Yes, that's the general flow of embargo processing, and what you want to do falls generally within it. > [2] Is there any way to generate notifications of lifting? The easiest > thing I can see would be to do a search for the embargo.field.terms > field, sorting on the availability, and supply that as an RSS feed. You could do something like that, but you could also directly act when the embargo is lifted. On the wiki page you cite, look at the Downloads section of the Prototype implementation for 'Embargo-1.6-new.zip'. This contains some example code from Harvard that extends the EmbargoLifter to send an email to the submitter whenever an embargoed item is lifted. This could give you an idea of how to do something similar (you didn't characterize how the notification target(s) would be identified, so I can't be more specific). > [3] We're considering how to direct users to other sources for the item > when it's currently embargoed. This would probably be involve displaying > a block of text which might be inviting them to login and giving them > alternative access routes to the item. Has anyone done this? This might be a bit more involved, especially if (as seems likely by your description) the text and access route would be item-specific. Having said this, if you could represent it in a metadata field or fields that would be entered at submission, your Lifter could programmatically remove them when the embargo ends. > [4] In the wiki at http://wiki.dspace.org/index.php/Embargo_1.6, if I am > reading things correctly, the second to last option in the config file > snippet is missing the relevant default option and the last option has > it truncated. Am I reading it correctly? The wiki page does look a little truncated: go with what you find in the dspace.cfg that ships with the 1.6 distribution and current tech doc. > > Due to my technical skills, I'd prefer options that involve XSLT to > those involving Java :) Except where noted above in [2] and [3] above about customizing the Lifter, the only Java coding you would need to do is in the EmbargoSetter (to interpret your fixed intervals into DSpace dates), but this is fairly simple (very rough code, just an example): [in 'parseTerms' method] ... if ("3 months".equals(terms)) { long monMillis = 90 * 24 * 60 * 60 * 1000; return new DCDate(new Date(System.currentTimeMillis() + monMillis)); } else if ("6 months".equals(terms)) { ..... > > cheers > stuart ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
