Hi Jason: I can see that this might be confusing, so let me try to explain a little more clearly.
At the most basic level, the field containing the 'terms' is where a submitter specifies how the embargo should work for that item. At the time of installation into the archive (i.e. when it exits workflow) those terms are 'interpreted' into a specific date in the future, which is then stored in the 'liftdate' field. The lifter then only checks this latter date, and ignores the original 'terms'. What can the terms be? Conceivably anything, (e.g. "60 days", "my standard policy", "Elsevier terms", etc), but of course the software cannot interpret arbitrary words. That's why the embargo system allows you to write your own code that interprets whatever terms you want to use, and will run that code at the appropriate time. However, 'out of the box', DSpace supplies code for the simplest case: that in which the terms are actual dates themselves. In this case, all it does is copy the date you put in 'terms' into 'liftdate'. Over time, as we discover other common 'terms', we can add to the DSpace 'library' of term-interpreting code, and distribute them with each new release. Finally, (to really confuse things), you can actually configure the 'terms' dc field to be the same as the 'liftdate' field! That is, make 'dc.embargo' or whatever you want serve as both terms and lift. In this case, it doesn't even copy a field, it just uses the date 'in place'. This is really a sensible configuration, if you don't want to keep a permanent record of what the terms were. Does that illuminate things a bit? Richard On Mar 31, 2010, at 1:59 PM, Jason Fowler wrote: > 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 [[email protected]] > Sent: Wednesday, March 31, 2010 12:14 PM > To: Jason Fowler > Cc: [email protected] > Subject: RE: [Dspace-tech] Embargoes in 1.6 > > Hello Jason, > > only the embargo terms afaik. The liftdate is computed based upon the terms. > > Claudia > >> Thanks, 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 > > ------------------------------------------------------------------------------ > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
