Hello Jason, the liftdate is computed based on the embargo terms and the setter used. At the moment there is one default embargo setter:
org.dspace.embargo.DefaultEmbargoSetter which assumes the basic use case of the term being a date. Which setter plugin to use is configured in the dspace.cfg:# implementation of embargo setter plugin - replace with local implementation if applicable plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.DefaultEmbargoSetter
In order to cover other use cases you got to write your own setter and use this instead of the default setter. You can do anything you like, for example using a set of timespans or depend the embargo time on the publication type. This is up to you.
Hope that helps Claudia Jürgen Am 31.03.2010 19:59, schrieb Jason Fowler:
That makes sense. The only thing I don't understand is how exactly the liftdate is computed. Is that something that happens automatically, or do I need to configure that? Jason Fowler, CA, MSLS ________________________________________ From: Claudia Juergen [claudia.juer...@ub.tu-dortmund.de] Sent: Wednesday, March 31, 2010 12:14 PM To: Jason Fowler Cc: claudia.juer...@ub.tu-dortmund.de Subject: RE: [Dspace-tech] Embargoes in 1.6 Hello Jason, only the embargo terms afaik. The liftdate is computed based upon the terms. ClaudiaThanks, Claudia! Just one more question. Do I need to add both dc.embargo.terms AND dc.embargo.liftdate to the input-forms.xml? Thanks in advance, Jason Fowler, CA, MSLS
<<attachment: Claudia_Juergen.vcf>>
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
