Re: [dspace-tech] Batch add/edit embargo dates

[Terry Brady]

I have not used it, but the Simple Archive Format seems to allow a
permission to be passed in when defining a CONTENTS file.

See
https://wiki.duraspace.org/display/DSDOC5x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat

If this will work with your workflow, you might be able to define some type
of restriction in the contents file.

I still use the legacy pre-DSpace 3.0 embargo process in order to set
embargoes via bulk ingest metadata.  That process requires you to have a
custom Embargo setter.  Here is an example of the one that I am using:
https://gist.github.com/terrywbrady/4e62fad6295d479aab78c905252acb86

Once the item has been submitted, the EmbargoSetter will create bitstream
access policies based on the metadata.  Any subsequent change to the
metadata will have no impact on the access policy records.  Those records
must be modified with existing tools.

One word of caution.  The pre-3.0 embargo functionality is targeted for
deprecation, so any solution built on it may only work through DSpace 6.0.
If you find that this is the approach that you use, please see the
following Jira ticket and add your thoughts:
https://jira.duraspace.org/browse/DS-2588

Terry

On Mon, Apr 17, 2017 at 2:09 PM, Andrew Parker  wrote:

> Setting up embargoes in DSpace has been a little bit more confusing than I
> expected.
>
> What I would like to be able to do is: a) batch upload new items to DSpace
> in Simple Archive Format with embargoes that are added for each item based
> on included metadata, and b) batch edit already uploaded items to add or
> modify embargo dates.
>
> What I'm not clear on is whether I need the pre-DSpace 3.0 embargo process
> to easily do both of the above.
>
> I'm comfortable with adding embargo policies to both collections and
> individual items, but given that no collection we have would exclusively
> consist of embargoed items, I don't see how to use policies to set
> embargoes for items without creating an embargo policy for each individual
> item via the admin interface. Being able to use the Batch Metadata Editing
> tool seems like it would be substantially faster  -- but ideally, we could
> prevent doing too much adding or editing of embargo dates after the fact by
> just specifying them in the initial upload.
>
> How do I approach doing these two things with the current embargo process?
>
>
>
>
>
>
>
>
>
>
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
http://georgetown-university-libraries.github.io/
425-298-5498 (Seattle, WA)

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Batch add/edit embargo dates

[Andrew Parker]

Setting up embargoes in DSpace has been a little bit more confusing than I 
expected.  

What I would like to be able to do is: a) batch upload new items to DSpace 
in Simple Archive Format with embargoes that are added for each item based 
on included metadata, and b) batch edit already uploaded items to add or 
modify embargo dates.

What I'm not clear on is whether I need the pre-DSpace 3.0 embargo process 
to easily do both of the above. 

I'm comfortable with adding embargo policies to both collections and 
individual items, but given that no collection we have would exclusively 
consist of embargoed items, I don't see how to use policies to set 
embargoes for items without creating an embargo policy for each individual 
item via the admin interface. Being able to use the Batch Metadata Editing 
tool seems like it would be substantially faster  -- but ideally, we could 
prevent doing too much adding or editing of embargo dates after the fact by 
just specifying them in the initial upload.  

How do I approach doing these two things with the current embargo process?  










-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.