Yeah, that’s the schema that made sense to me as well. Would it be relatively easy for me to update FileAnalyzer’s Proquest script to use that schema instead? Thanks again for all the assistance.
From: Terry Brady <[email protected]> Date: Friday, September 27, 2019 at 4:56 PM To: Shawn Kiewel <[email protected]>, Dspace Tech <[email protected]> Subject: Re: [dspace-tech] update and thanks Shawn, I use the following embargo.field.terms = gu.embargo.terms embargo.field.customdate = gu.embargo.custom-date # DC metadata field to hold computed "lift date" of embargo embargo.field.lift = gu.embargo.lift-date We created a custom schema called "gu" for Georgetown University before I understood the existence of the local schema. If I were implementing this now, I would use local.embargo.terms, local.embargo.custom-date, etc. On Thu, Sep 26, 2019 at 2:29 PM Shawn Kiewel <[email protected]> wrote: Firewall exceptions have finally been made for my dev server, so I finally was able to test ‘on-campus-read-only’ embargoes. And it works! Thank you so much for all your help getting me to this point. I appreciate it more than you can know. Now, I’m not out of the woods yet, because I need to make sure it works with adding bitstreams to existing records, but I have a good idea how to proceed with that. Does mean that you might still be hearing from me again though – sorry in advance. I do have one question: Terry, what metadata schema and fieldnames are you using for your embargo settings? It occurred to me that my ad hoc ones probably don’t match up with FileAnalyzer’s script to prep Proquest batches. Thanks again so much, 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/8FDC9EED-8139-416E-BB34-3FE1F44A78D2%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/85EF0E37-56A6-4237-B949-6D541CFFCAAD%40gmail.com.
