dspace metadata fields

[sunit...@gmail.com]

Dear all

Our metadata in dspace is scattered under different following metadata fields.

How can we club together such data in one go.

dc.contributor.advisor

dc.contributor.advisor[]

dc.contributor.advisor[en_US]

dc.contributor.author

dc.contributor.author[]

dc.contributor.author[en]

dc.contributor.author[en_US]

dc.date.accessioned

dc.date.accesioned[]

dc.date.accessioned[en_US]

dc.date.available...................

reg

Sunita Barve

[Jose Blanco]

If I understand correctly, you want to bring all this data together under a new metadata?  So you could create a new metadata, lets say:

metadata.all

Then I would write a script that accesses the database and gathers the data and prepares the data to store in metadata.all.  I would use the itemupdate to get the new metadata in the repository:

https://wiki.lyrasis.org/display/DSDOC6x/Updating+Items+via+Simple+Archive+Format

This all seems a little strange to me.  I wonder what your end goal is here.  You might not need to do this.

-Jose

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/e9281b11-0b9a-4241-bda1-4e879e598b6en%40googlegroups.com.

[dbig...@gmail.com]

I think you could export the metadata into OpenRefine of even LibreOffice Calc. Then trim the leading and ending white spaces and compact any consecutive white spaces. Then address the language qualifier. If everything is in English you could set that column to [en] or you could just empty the column. You will have to make changes to you metadata scheme in DSpace to keep this from reoccurring. Once your data is clean, import and overwrite.

David Bigwood

dbig...@lpi.usra.edu

Library, Planetary Image Facility

Lunar and Planetary Institute

[Sean Kalynuk]

Hey everyone,

 

Some issues to be aware of regarding the metadata language value:

 

https://jira.lyrasis.org/browse/DS-2174

https://jira.lyrasis.org/browse/DS-2548

https://jira.lyrasis.org/browse/DS-4169

https://jira.lyrasis.org/browse/DS-4493

 

And some other info:

 

https://wiki.lyrasis.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-MetadatavaluesinCSVexportseemtohaveduplicatecolumns

 

I agree with David that using OpenRefine on exported metadata cleanup is a great option. You’ll just have to be aware of the issues where a “null” language (e.g., dc.contributor.advisor) versus an “empty” language (e.g., dc.contributor.advisor[]) will be updated differently later on depending on where in DSpace the change is being made. Specifically, DS-4169 (fixed in DSpace 6.4) describes the issue whereby “null” language values get changed to “empty” language values when editing metadata via the user interface. So, I think that having a language qualifier (e.g., en or en_US) would eliminate the uncertainty with subsequent metadata updates (at least until all the issues are resolved).

 

--

Sean

 

From: dspac...@googlegroups.com <dspac...@googlegroups.com>
Date: Thursday, October 29, 2020 at 10:23 AM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] Re: dspace metadata fields

Caution: This message was sent from outside the University of Manitoba.

--

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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/d6aa10e9-8a73-4739-9806-7ebfe93fd2b9n%40googlegroups.com.