For anyone following along at home and future googlers, using ItemUpdate with
the replace option will replace the existing item and retrigger the embargo
setting. Also, the mapfile format for importing is a simple text file with:
directory_name item_handle
directory_name item_handle
Shawn
On
Am 02.10.19 um 11:54 schrieb Michael Plate:
Hi,
https://api.creativecommons.org/
[…]
up and running.
--
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
Thank you, Claudia. I was able to successfully update the metadata using the
batch tool. Perhaps the docs should be updated to specify that other schemas
can be used?
However, just as I feared, just updating the metadata did not trigger the
embargo setting. Additional searching lead me to
Hello Shawn,
the easiest way to update metadata is the batch metadata editing. It
should work with any metadata field which is registered in your
instances metadata registry regardless of the schema.
So first register your schema in your instance and add the field(s) to
this schema.
On the UI
Hi,
https://api.creativecommons.org/
is currently (11:55 CEST) down (503 Service Unavailable)- if you have
the CC-license step in your submission the submission will fail and
produce a stack trace (at least on Dspace 5.x, XMLUI).
CU
Michael
--
All messages to this mailing list should
