Hi Jacob:
Not sure I completely understand your needs, but if I do, it is fairly simple
using 1.6 embargo to do what you want. Steps:
(1) Decide on a metadata field to store embargo dates: you will have to add it
to the metadata registry in the admin UI.
I'll call it 'dc.embargo' in this explanation, but note that that is an
abuse of the Dublin Core namespace to some extent.
(2) Configure embargo in dspace.cfg:
embargo.field.terms = dc.embargo
embargo.field.lift = dc.embargo
(3) then all you have to do is enter the embargo dates (in ISO date format:
YYYY-MM-DD) in the 'dc.embargo' metadata field of items you are importing (in
SAF in ItemImport, etc).
When the Import is run, all your content bearing an embargo date will be
placed under embargo. If you also want to enter embargo dates in the submit Web
UI, just add the
'dc.embargo' field to input_forms.xml. If all your content, is batch,
don't bother.
(4) SInce it's ordinary metadata, you should be able to export it in all the
forms you mention - AIP, SAF, CSV, etc just fine.
(5) When you feel like it, run the Embargo Lifter script to remove the embargo
restrictions of eligible items. If this is a pain because there are a lot of
dates, just add the script to a 'cron' job that will
run automatically on a schedule that makes sense for you (nightly, weekly,
etc).
Hope this helps,
Richard Rodgers
On Sep 10, 2013, at 5:07 PM, Brown, Jacob wrote:
This is my first email to this list, so I apologize if this has been covered
previously or if I’m using the list incorrectly.
Is it possible to define embargo settings (e.g., a “lift date”) as part of a
batch import process (e.g., using the Simple Archive Format ingest process or
the AIP or CSV ingest processes)?
I searched for this issue online, and came across this thread:
http://dspace.2283337.n4.nabble.com/KE1019161-Embargo-settings-on-item-import-td4660719.html.
Helix84’s post at Jan 03, 2013; 7:38am touches directly on this issue, but
seems incorrect as far as I can tell (AIP mets.xml doesn’t seem to describe
embargo settings).
I’ve created an item in my test repository (DSpace 3.2) using the xmlui
interface and defined an embargo for a bitstream using the “Simple Embargo/
UploadWithEmbargoStep” process. I’ve confirmed that the item was added
successfully, and that the policy restrictions are enforced for anonymous users.
I then exported the item as an AIP, SAF, and CSV (using the various export
mechanisms). None of the exported data (AIP’s mets.xml, the SAF files, or the
CSV) seemed to have any information about my embargo.
Is there a way to include this information in the import process, or would I
have to set this manually in xmlui or write a SQL script to add these embargo
policies?
Thanks,
Jacob Brown
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk_______________________________________________
DSpace-tech mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
