Hello
We are using DSpace v6(.4) and in particular we are publishing articles,
reports, maps etc by using the REST-api (we have our own inventory system
from way way back).
But, what we are experiencing, is that multi value metadata elements such as
dc.contributor.author, is not stored in the DSpace database in the same sorted
way we add them in the JSON structure.
>From what I've seen, the sorting of dc.contributor.author is completely random,
and never the same order/sorting as I put in. It's repeatable reproducable.
I have tried adding authors in several different ways:
1. together with all other metadata using httpPost
2. first all other metadata and then all authors in a seperate httpPost
3. first all other metadata and then individual authors in seperate httpPosts.
When using the Web User Interface, there's no problem with correct
ordering/sorting of authors. We've been told that the xmlui propably write
directly to the database and doesn't use the REST-api at all and thus ordering
is handled correctly. It baffles me that the REST-interface does not handle the
data the same way its POSTed.
Anyone experienced the same? I have over 7000 publications published with
wrong order of authors, and I would very much like to not
reorder them
manually using the xmlui.
Good ideas?
Database:PostgreSQL
Java: OpenJDK (1.8.x)
Kind regardsBjørn Ove Grøtan -- 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/20200922105942.GE6653%40samfundet.no.
