Kia ora koutou, We’re starting to play with the embargo functionality, in v5.6 XMLUI (Mirage) – but to complicate matters most of our items are submitted from Symplectic Elements. It may turn out that we have to do a lot manually but first I want to test what we can do automatically and I’m running into some Unexpected Behaviour.
Our dspace.cfg embargo settings are: #### Embargo Settings #### # DC metadata field to hold the user-supplied embargo terms embargo.field.terms = lu.embargo.ends # DC metadata field to hold computed "lift date" of embargo embargo.field.lift = lu.embargo.enddate # string in terms field to indicate indefinite embargo embargo.terms.open = forever embargo.terms.days = 3 months:91,6 months:182,9 months:274,12 months:365,1 year:365,15 months:456,18 months:548,21 months:639,24 months:730 # implementation of embargo setter plugin - replace with local implementation if applicable plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.DefaultEmbargoSetter # implementation of embargo lifter plugin - - replace with local implementation if applicable plugin.single.org.dspace.embargo.EmbargoLifter = org.dspace.embargo.DefaultEmbargoLifter (For submitting through the web interface I’ve enabled the submission step to let users add an embargo at the bitstream level; I’ve left out the step to add an embargo at the item level because this doesn’t suit our workflow. I don’t *think* this is relevant here but it might be...) When I submit an item via Elements, the term “6 months” is put into the field lu.embargo.ends (I’ve verified this by checking directly in the database). When I check the metadata when it’s in workflow, I don’t see any end-date calculated – so I assume that it’ll calculate this on committal to the archive. But when I click ‘commit to archive’ I get the error: “Embargo lift date must be in the future, but this is in the past: 6” So it appears to be attempting to interpret the term “6 months” as a date by throwing out the alpha characters and complaining that 6 < 2016-11-04 - instead of converting “6 months” -> 182 days and adding that to the current date as I thought it was meant to do. Am I missing something; or is this a bug; or is it a bad interaction with Elements? Kā mihi maioha, Deborah Fitchett Senior Advisor, Digital Access Library, Teaching and Learning p +64 3 423 0358 e [email protected]<mailto:[email protected]> | w ltl.lincoln.ac.nz<http://library.lincoln.ac.nz/> Lincoln University, Te Whare Wānaka o Aoraki New Zealand's specialist land-based university ________________________________ P Please consider the environment before you print this email. "The contents of this e-mail (including any attachments) may be confidential and/or subject to copyright. Any unauthorised use, distribution, or copying of the contents is expressly prohibited. If you have received this e-mail in error, please advise the sender by return e-mail or telephone and then delete this e-mail together with all attachments from your system." -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
