[
https://jira.duraspace.org/browse/DS-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24896#comment-24896
]
Richard Jones commented on DS-1175:
-----------------------------------
Hi Richard,
Thanks for that, it's useful. I had understood that the terms were free-text
(i.e. user supplied), and the embargo lift date was the operational part, which
I've got wrong. I have been attempting to supply a lift date during deposit,
but the embargo manager isn't looking at it as far as I can tell.
I have two bits of metadata coming in with my deposit, one is the embargo
"terms", which could be a variety of strings including things like "on-site
access only", and another which is the date the embargo is to be lifted. I've
been mapping these to the terms and the lift date respectively, which is what's
causing me confusion.
I can re-organise my import to put the lift date in the terms field, and put
the terms of the embargo somewhere else.
Cheers,
Richard
> EmbargoManager looks for Embargo Lift Date in Embargo Terms
> -----------------------------------------------------------
>
> Key: DS-1175
> URL: https://jira.duraspace.org/browse/DS-1175
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.8.2
> Environment: All
> Reporter: Richard Jones
> Priority: Major
> Labels: embargo
>
> The DSpace configuration defines two fields for use in Embargo:
> embargo.field.terms - for user-supplied terms of embargo
> embargo.field.lift - for the lift date of the embargo
> The EmbargoManager attempts to load the lift date of the embargo from the
> embargo.field.terms field, and does not check the embargo.field.lift. This
> then throws an error if no date is available in the embargo.field.terms.
> Looking deeper into this, there appears to be minimal usage of the
> embargo.field.lift field, and the documentation is confusing. Probably the
> fix is a rationalisation of what each of these fields actually means, and a
> re-implementation of at least the EmbargoManager and DefaultEmbargoSetter for
> consistency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
