Hi Andrea, thanks for your reply and possible solution, I suspected this was
the case. Are you aware of the new release of rioxx metadata
profile<http://rioxx.net/v2-0-final/>? I wonder if future DSpace releases will
incorporate this with the advanced embargo functionality?
Many thanks,
Antony
On 25 Mar 2015, at 21:08, Andrea Schweer wrote:
Hi Antony,
On 26/03/15 05:24, Antony Corfield [awc] wrote:
I've configured DSpace 4.0 to use simple embargo
functionality<https://wiki.duraspace.org/display/DSDOC4x/Embargo#Embargo-SimpleEmbargoSettings>
including submission forms and dspace.cfg below. Although the embargo is
lifted on the correct date and seems to be working fine I can't see the
dc.rights.embargoreason and dc.rights.embargodate in the full item metadata
view or in the database. I can see the date in the policies for the item
(attached).
It seems that the reason and date aren't being copied to these metadata fields.
Prior to upgrade (from 1.8) this was working and any items that were embargoed
prior to upgrade do have these metadata fields in the full item view and in the
database.
Any help would be very much appreciated as we really need embargo details in
the item metadata.
The simple embargo functionality doesn't use item metadata at all. All
information is stored in the policies. So the behaviour you're asking for
doesn't exist in that mechanism. The settings you quote in your e-mail don't
apply when you use the simple embargo functionality.
If having the embargo information in the policies is not sufficient for your
needs, your best bet is probably to add fields for the embargo date and reason
to input-forms.xml, possibly on a new page if you want to keep them separated
from the other item metadata.
cheers,
Andrea
#### Embargo Settings ####
# DC metadata field to hold the user-supplied embargo terms
#embargo.field.terms = SCHEMA.ELEMENT.QUALIFIER
#awc
embargo.field.terms = dc.rights.embargoreason
# DC metadata field to hold computed "lift date" of embargo
embargo.field.lift = dc.rights.embargodate
# string in terms field to indicate indefinite embargo
embargo.terms.open = forever
# 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
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
