Hello, Thank you all for your interest in the topic and for your insights so far. It looks like transition to dcterms is less straightforward than expected.
The reason behind this issue is that I would prefer to stick with official DCMI namespaces <https://www.dublincore.org/specifications/dublin-core/dcmi-terms/> only. DSpace introduces many unofficial elements, and although I presume they are well established already, this is difficult to determine whether they will be correctly recognized by increasingly abundant external tools. I wouldn't mind using dc namespace, but dcterms has broader scope, so this is why I thought I would focus on this set of terms at first. However, attempting to adjust our current metadata to fit a stricter dc scope could be worthwhile. Best, Peter poniedziałek, 8 kwietnia 2024 o 21:33:11 UTC+1 Reed, Marianne A. napisał(a): > Peter, could you please share why your institution wants to switch to > “dcterms” instead of “dc” ? I’m curious about the use case for this. > > > > If you prefer, feel free to email me directly rather than replying to the > list. > > > > Best, > > Marianne > > > > Marianne Reed (she/her/hers*)* > > Digital Publishing & Repository Manager > > Watson Library, Room 470-G > > University of Kansas Libraries > > [email protected] > > 785-864-8913 <(785)%20864-8913> > > > > *From:* DSpace Community <[email protected]> > *Sent:* Monday, April 8, 2024 3:02 PM > *To:* DSpace Community <[email protected]> > *Subject:* Re: [dspace-community] Switching from "dc" to "dcterms" in > DSpace > > > > Hi Peter, > > > I can verify that what Jorge says is true. DSpace's User Interface (not > only in 6.x, but also in 7.x) assumes you are using "dc" fields. While > it's not *impossible* to make the switch to "dcterms", I suspect it'd take > a lot of effort to make it happen. DSpace has always relied on the > existence of many key "dc" fields for title, author, descriptions, etc. To > remove all those hardcoded assumptions would be a lot of work. If you still > want to do it, your first step may be to search the codebase and > configuration of any hardcoded references to "dc.*" fields, and replace > them with "dcterms.*" equivalents. > > > > Tim > > On Monday, April 8, 2024 at 9:56:42 AM UTC-5 [email protected] wrote: > > Hello everyone, > > > > In my opinion it would be a problem to make that change. > > I think that several functionalities linked to specific dc fields would be > affected. > > > > Your idea is very interesting, but doing it en masse would involve > reconditioning several elements in configurations in my opinion. In > addition to reconditioning the worksheet, which would be the least > important thing in this case. > > > > I only recommend it if you have significant knowledge or assistance, and > in a trial instance. > > > > Greetings, > > Jorge > > > > El dom, 31 mar 2024 a las 9:44, Peter (<[email protected]>) escribió: > > Hello, > > > > We are considering switching from "dc" to "dcterms" namespace in our > repository. > > > > Is it technically possible without breaking any DSpace core functionality? > > > > Although we do not use the newest DSpace version yet, but we are getting > ready to update to one, so I would be interested to find out how would the > newest versions handle this. > > > > Tested replacing dc namespace with their equivalents in dcterms, and at > least in DSpace 6 this results in disappearance of some data from landing > page, but more important would be whether this is only a visual effect or > the result of a more serious fault? > > > > Thank you. > > Peter > > > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" 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-community/e9ce1719-5125-4c81-b0e2-b6f4efb3b68fn%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-community/e9ce1719-5125-4c81-b0e2-b6f4efb3b68fn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > All messages to this mailing list should adhere to the Code of Conduct: > https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" 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-community/c8929405-72fa-411d-8d62-165f94b56689n%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-community/c8929405-72fa-411d-8d62-165f94b56689n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" 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-community/5a587f0f-b73c-4d40-99cd-78addd65a9a2n%40googlegroups.com.
