Hi, It does seem to be using the date in the field specified by embargo.field.terms in dspace.cfg. I’ve successfully got our crosswalk to send across a specific date in yyyy-mm-dd format into that field, and when the item is approved into the collection, the bitstream policy is created with a start-date of that date.
It presumably only doesn’t do the same for the item policy because we’ve kept that step out of our submission workflow. (Or possibly it /would/ break if that step was there and we just haven’t tried it. :-) ) The potentially confusing thing is that, because the metadata is used to create the policy when the item is approved, when you look at the bitstream in workflow, no date appears there. But that’s just something for our admin staff to look out for. The manual work for us comes because all our via-Elements items get approved into a restricted collection in the first instance, and then we move them into an open collection. Inheriting anon policies is fine if we’re making it open immediately, but if we’re embargoing the bitstreams then we need to edit the policies at that point. Deborah From: Andrea Schweer [mailto:[email protected]] Sent: Wednesday, 9 November 2016 10:58 a.m. To: Fitchett, Deborah <[email protected]>; DSpace Technical Support <[email protected]> Subject: Re: [dspace-tech] RE: Embargo settings Hi, On 11/09/2016 10:22 AM, Fitchett, Deborah wrote: So from some more poking and re-rereading the documentation, I *think* the situation is that the embargo.field.terms functionality is only used in the pre-DSpace 3.0 embargo model – does this sound right to others? Yes that's right. If this is the case then I need to follow up with Symplectic Elements to see if they’ll upgrade their embargo interface to let users submit a date instead of a term, and in the meantime either do something fancy with the crosswalks, or get our repository staff to apply the desired embargo date manually in workflow. We have very customised embargo functionality, so I'm not too sure on DSpace default behaviour. But I think you will need to use the 'manual in workflow' option since (IIRC) metadata-based embargoes don't work at all in the new model. Embargoes now use the authorisation policies. cheers, Andrea -- Dr Andrea Schweer Lead Software Developer, ITS Information Systems The University of Waikato, Hamilton, New Zealand +64-7-837 9120 ________________________________ 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.
