Great, thanks for the info!

On Thu 17 May, 2018 00:09 Tim Donohue, <tdono...@duraspace.org> wrote:

> Hi Manjunath:
>
> Assuming you are using a recent version of DSpace (I believe this works
> in  4.x or above), the Embargo date can be managed by editing the Item's
> "Authorization Policies".  This is described (very briefly) here:
>
> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-DSpaceEmbargoFunctionality
>
> Here's how you'd do that (these are for the XMLUI, but similar options are
> available in JSPUI)
> 1) Login as an Admin
> 2) Browse to the embargoed item (Admins should be able to see any
> embargoed items)
> 3) Click on "Edit Item"
> 4) On the "Item Status" tab, click the "Authorizations" button
> 5) You'll then see a detailed list of all access policies on this item.
> Embargoes appear as *start dates* for a policy.  So, for example, if an
> Item is to become public *after January 1, 2020, you'll see a policy that
> says "Anonymous" access on 2020-01-01.
>
> To remove an embargo, click on the Policy to edit it, and clear out the
> "start date".
> To change an embargo, click on the Policy to edit it, and change the
> "start date" to a new date.
> To add an embargo, click on the Policy to edit it, and set a "start date".
>
> The change should take effect immediately.  Of course, as an Admin, you
> will have access to embargoed items. But, if you logout, the embargo should
> appear immediately.
>
> I hope that helps,
>
> Tim
>
> On Wed, May 16, 2018 at 12:43 PM George Kozak <gkoz...@gmail.com> wrote:
>
>> Manjunath:
>>
>> I am not sure if this is the best way to do this, but we at Cornell
>> University, we do this manually by going into the Postgres database and
>> manipulating the Resource Policy table.
>> Here is a simplified version of our procedure:
>>
>> To embargo an item, after submission:
>>    - As Admin, go to edit an item and put the embargo date in the
>> dublin_core field that you are using for embargoes.
>>    - Get the ID for the bitstream(s) that you want to embargo.
>>    - Go to psql
>>       -select start_date from resourcepolicy where resource_id=<bitstream
>> id>;
>>    - Once you’ve determined that you found the correct bitstream and
>> date, you can execute:
>>       - update resorcepolicy set start_date=<whatever you want> where
>> resource_id=<bitstream id>;
>>    - This has to be done for every bitstream that the item contains.
>>
>> To revise the embargo on an item:
>>  - Do the same as above
>>
>> To lift an embargo on an item:
>>  - Modify the dublin_core embargo field as described above, and find the
>> bitstream ids
>>  - Go to psql
>>     - select start_date from resourcepolicy where resource_id=<bitstream
>> id>;
>>  - Once you’ve determined that you found the correct bitstream and date,
>> you can execute:
>>     - update resorcepolicy set start_date=null where
>> resource_id=<bitstream id>;
>>
>> George Kozak
>> Cornell University
>>
>> On Tue, May 15, 2018 at 8:23 AM, Manjunath Sajjan <mgsajj...@gmail.com>
>> wrote:
>>
>>> I would like to know even if it is possible to change the date of an
>>> embargo on an item after that it is submitted. And add/remove embargo
>>> date. How to achieve these?.
>>>
>>>
>>>
>>>
>>> __
>>>
>>> Best Regards,
>>> Manjunath Sajjan
>>>
>>> --
>>> 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.
>>>
>>
>>
>>
>> --
>> ***************************
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924 <(607)%20255-8924>
>> g...@cornell.edu
>>
>> --
>> 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.
>>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>

-- 
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.

Reply via email to