Re: [dspace-tech] updating items and custom embargo

2019-08-29 Thread Terry Brady 
Anne,

We use the legacy embargo policy feature to calculate an embargo end date.

That code is summarized here.
https://gist.github.com/terrywbrady/a37d1170b2c5fa117495ab415fbfc113

The embargo code creates the authorization policy records and sets an end
date on the policy.

Terry

On Thu, Aug 29, 2019 at 11:18 AM Anne Lawrence  wrote:

> Terry,
>
> Thank you for this description of using File-Analyzer for this
> application. Are you able to specify an end date for embargoed files in the
> SAF folders? We've used the "\tpermissions:PERMISSIONS" in the contents
> file and have wanted to add an end date to this,
> https://wiki.duraspace.org/display/DSDOC6x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat
> .
>
> Anne
>
> On Tuesday, August 27, 2019 at 12:12:02 PM UTC-4, Terry Brady wrote:
>>
>> If you have written a custom embargo policy routine, the SAF ingest
>> process will trigger that routine.
>>
>> Definitely test this out with a few items first.
>>
>> We have an automated conversion process that converts ProQuest embargo
>> values into our existing embargo policies.
>>
>>
>> https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/Generate-DSpace-Ingest-folders-from-ProQuest-ETD-files
>>
>>
>> Terry
>>
>> On Tue, Aug 27, 2019 at 8:31 AM Shawn Kiewel  wrote:
>>
>>> Sorry for the bother again. As I’ve mentioned, I’m moving my current ETD
>>> repo into DSpace completely, which to-date has just held metadata. I’ve
>>> been informed of the ItemUpdate via Simple Archive Format for moving my
>>> bitstreams over. However, it occurs to me that the second half of my
>>> problem can’t be solved that way, which is the embargo issues. So I have a
>>> simple (I hope) question: if I use the item update tool to update both the
>>> bitstreams and the dc.embargo.terms metadata field, will the embargo ‘take’
>>> and my custom embargo setter still be used?
>>>
>>>
>>>
>>> Thanks again for the assistance.
>>>
>>> Shawn
>>>
>>> --
>>> All messages to this mailing list should adhere to the DuraSpace Code of
>>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>>> ---
>>> 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 dspac...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/dspace-tech/6BE2E925-3065-4C16-8BFD-04EEE25EB50D%40gmail.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Terry Brady
>> Applications Programmer Analyst
>> Georgetown University Library Information Technology
>> https://github.com/terrywbrady/info
>> 425-298-5498 (Seattle, WA)
>>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/065f336d-9eca-42e7-af2e-b576bf646b8f%40googlegroups.com
> 
> .
>


-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAMp2YEynHQT96%2BoZFOnbU02gmLcNxkx%2BzOeWFTLeGRdArfH55A%40mail.gmail.com.

Re: [dspace-tech] updating items and custom embargo

2019-08-29 Thread Anne Lawrence 
Terry,

Thank you for this description of using File-Analyzer for this application. 
Are you able to specify an end date for embargoed files in the SAF folders? 
We've used the "\tpermissions:PERMISSIONS" in the contents file and have 
wanted to add an end date to this, 
https://wiki.duraspace.org/display/DSDOC6x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat.

Anne

On Tuesday, August 27, 2019 at 12:12:02 PM UTC-4, Terry Brady wrote:
>
> If you have written a custom embargo policy routine, the SAF ingest 
> process will trigger that routine.
>
> Definitely test this out with a few items first.
>
> We have an automated conversion process that converts ProQuest embargo 
> values into our existing embargo policies.
>
>
> https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/Generate-DSpace-Ingest-folders-from-ProQuest-ETD-files
>  
>
> Terry 
>
> On Tue, Aug 27, 2019 at 8:31 AM Shawn Kiewel  > wrote:
>
>> Sorry for the bother again. As I’ve mentioned, I’m moving my current ETD 
>> repo into DSpace completely, which to-date has just held metadata. I’ve 
>> been informed of the ItemUpdate via Simple Archive Format for moving my 
>> bitstreams over. However, it occurs to me that the second half of my 
>> problem can’t be solved that way, which is the embargo issues. So I have a 
>> simple (I hope) question: if I use the item update tool to update both the 
>> bitstreams and the dc.embargo.terms metadata field, will the embargo ‘take’ 
>> and my custom embargo setter still be used?
>>
>>  
>>
>> Thanks again for the assistance.
>>
>> Shawn
>>
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> 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 dspac...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/6BE2E925-3065-4C16-8BFD-04EEE25EB50D%40gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://github.com/terrywbrady/info
> 425-298-5498 (Seattle, WA)
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/065f336d-9eca-42e7-af2e-b576bf646b8f%40googlegroups.com.

Re: [dspace-tech] updating items and custom embargo

2019-08-27 Thread Terry Brady 
If you have written a custom embargo policy routine, the SAF ingest process
will trigger that routine.

Definitely test this out with a few items first.

We have an automated conversion process that converts ProQuest embargo
values into our existing embargo policies.

https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/Generate-DSpace-Ingest-folders-from-ProQuest-ETD-files


Terry

On Tue, Aug 27, 2019 at 8:31 AM Shawn Kiewel  wrote:

> Sorry for the bother again. As I’ve mentioned, I’m moving my current ETD
> repo into DSpace completely, which to-date has just held metadata. I’ve
> been informed of the ItemUpdate via Simple Archive Format for moving my
> bitstreams over. However, it occurs to me that the second half of my
> problem can’t be solved that way, which is the embargo issues. So I have a
> simple (I hope) question: if I use the item update tool to update both the
> bitstreams and the dc.embargo.terms metadata field, will the embargo ‘take’
> and my custom embargo setter still be used?
>
>
>
> Thanks again for the assistance.
>
> Shawn
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/6BE2E925-3065-4C16-8BFD-04EEE25EB50D%40gmail.com
> 
> .
>


-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAMp2YExZ%2BJTL%2BDkGhgdd%2BRUU-z9GXQtFSVi6%3DdMEENfcd%3D1Z1Q%40mail.gmail.com.

[dspace-tech] updating items and custom embargo

2019-08-27 Thread Shawn Kiewel 
Sorry for the bother again. As I’ve mentioned, I’m moving my current ETD repo 
into DSpace completely, which to-date has just held metadata. I’ve been 
informed of the ItemUpdate via Simple Archive Format for moving my bitstreams 
over. However, it occurs to me that the second half of my problem can’t be 
solved that way, which is the embargo issues. So I have a simple (I hope) 
question: if I use the item update tool to update both the bitstreams and the 
dc.embargo.terms metadata field, will the embargo ‘take’ and my custom embargo 
setter still be used?

 

Thanks again for the assistance.

Shawn

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/6BE2E925-3065-4C16-8BFD-04EEE25EB50D%40gmail.com.