Re: [dspace-tech] add local metadata to existing item
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 10/2/19, 10:30 AM, "Shawn Kiewel" wrote: 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 this post by Terry that confirms such (wish I'd found it earlier): http://dspace.2283337.n4.nabble.com/Batch-add-edit-embargo-dates-td4685346.html Looks like the only solution is to use the ItemUpdate with the Simple Archive Format to replace the items. That should trigger the embargo process. My only unsure thing at the moment is how to format the mapfile, since these records were all imported via batch metadata import, so no mapfiles exist, but I'm about to do some experimentation that should give me that info. Thanks, Shawn On 10/2/19, 10:03 AM, "Claudia Jürgen" wrote: 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 log in as administrator then Administer -> General Settings -> Metadata Registry At the bottom of the list is the point where you can create the schema "Create a new schema by entering a namespace/name or edit an existing one by clicking the update button. The schema name must be less than 32 characters and cannot include spaces, periods or underscores. " Once created click on the schema in the list and add your fields. Hope this helps Claudia Jürgen Am 01.10.2019 um 21:24 schrieb Shawn Kiewel: > I’m looking to add local schema metadata to existing items. From my readings this doesn’t seem possible. First I looked at using ItemUpdate to update the metadata, but according to https://wiki.duraspace.org/display/DSDOC6x/Updating+Items+via+Simple+Archive+Format, it only does metadata fields defined in dublin_core.xml. Then I thought of using batch metadata editing, but https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing under file structure says that the fields need to be Dublin core. My searches for related posts came up empty. I do know that importing a new item with the local fields is working, but I’m not sure I can think of another way to import the local schema with just metadata. Think I have to resort to removing the items and importing them as “new” objects? Admittedly, this is my fallback position anyway, because I fear there is a chance that simply editing the metadata won’t trigger the embargo code, so I’d have to reimport the objects anyway, since that is proven working. > > > > Shawn > -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 claudia.juer...@tu-dortmund.de www.ub.tu-dortmund.de Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax. -- 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" grou
Re: [dspace-tech] CC Service is down
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 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/d9e99d99-6b65-a572-6f0f-5180ab73323d%40bibliothek.uni-kassel.de. smime.p7s Description: S/MIME Cryptographic Signature
Re: [dspace-tech] add local metadata to existing item
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 this post by Terry that confirms such (wish I'd found it earlier): http://dspace.2283337.n4.nabble.com/Batch-add-edit-embargo-dates-td4685346.html Looks like the only solution is to use the ItemUpdate with the Simple Archive Format to replace the items. That should trigger the embargo process. My only unsure thing at the moment is how to format the mapfile, since these records were all imported via batch metadata import, so no mapfiles exist, but I'm about to do some experimentation that should give me that info. Thanks, Shawn On 10/2/19, 10:03 AM, "Claudia Jürgen" wrote: 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 log in as administrator then Administer -> General Settings -> Metadata Registry At the bottom of the list is the point where you can create the schema "Create a new schema by entering a namespace/name or edit an existing one by clicking the update button. The schema name must be less than 32 characters and cannot include spaces, periods or underscores. " Once created click on the schema in the list and add your fields. Hope this helps Claudia Jürgen Am 01.10.2019 um 21:24 schrieb Shawn Kiewel: > I’m looking to add local schema metadata to existing items. From my readings this doesn’t seem possible. First I looked at using ItemUpdate to update the metadata, but according to https://wiki.duraspace.org/display/DSDOC6x/Updating+Items+via+Simple+Archive+Format, it only does metadata fields defined in dublin_core.xml. Then I thought of using batch metadata editing, but https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing under file structure says that the fields need to be Dublin core. My searches for related posts came up empty. I do know that importing a new item with the local fields is working, but I’m not sure I can think of another way to import the local schema with just metadata. Think I have to resort to removing the items and importing them as “new” objects? Admittedly, this is my fallback position anyway, because I fear there is a chance that simply editing the metadata won’t trigger the embargo code, so I’d have to reimport the objects anyway, since that is proven working. > > > > Shawn > -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 claudia.juer...@tu-dortmund.de www.ub.tu-dortmund.de Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax. -- 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/360f1a8f-fbf9-85ef-a9c0-e457365829fb%40tu-dortmund.de. -- 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, se
Re: [dspace-tech] add local metadata to existing item
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 log in as administrator then Administer -> General Settings -> Metadata Registry At the bottom of the list is the point where you can create the schema "Create a new schema by entering a namespace/name or edit an existing one by clicking the update button. The schema name must be less than 32 characters and cannot include spaces, periods or underscores. " Once created click on the schema in the list and add your fields. Hope this helps Claudia Jürgen Am 01.10.2019 um 21:24 schrieb Shawn Kiewel: I’m looking to add local schema metadata to existing items. From my readings this doesn’t seem possible. First I looked at using ItemUpdate to update the metadata, but according to https://wiki.duraspace.org/display/DSDOC6x/Updating+Items+via+Simple+Archive+Format, it only does metadata fields defined in dublin_core.xml. Then I thought of using batch metadata editing, but https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing under file structure says that the fields need to be Dublin core. My searches for related posts came up empty. I do know that importing a new item with the local fields is working, but I’m not sure I can think of another way to import the local schema with just metadata. Think I have to resort to removing the items and importing them as “new” objects? Admittedly, this is my fallback position anyway, because I fear there is a chance that simply editing the metadata won’t trigger the embargo code, so I’d have to reimport the objects anyway, since that is proven working. Shawn -- Claudia Juergen Eldorado Technische Universität Dortmund Universitätsbibliothek Vogelpothsweg 76 44227 Dortmund Tel.: +49 231-755 40 43 Fax: +49 231-755 40 32 claudia.juer...@tu-dortmund.de www.ub.tu-dortmund.de Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank. Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen. Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax. -- 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/360f1a8f-fbf9-85ef-a9c0-e457365829fb%40tu-dortmund.de.
[dspace-tech] CC Service is down
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 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/7b9d5dfd-6248-ee29-e40d-883f32195d71%40bibliothek.uni-kassel.de. smime.p7s Description: S/MIME Cryptographic Signature
