place of publication

[cetapslm]

I'm new to DC Core. I would like to know what is the best term and descriptor for "place of publication" of a book. I also wonder if I can create qualifiers when needed. For example, dc.contributor.illustrator to state the name of a contributing illustrator of a book. Thank you in advance for you help. Luciano Moreira

[HughP]

What is your context? That looks like a DSpace type of serialization with the dots. With regards to roles like illustrators it might be better to not create unique qualifiers and just use MARC roles. With regards to place of publication in books, my understanding is that this does not exist within the metadata elements available. However it could be added in a non-machine readable way to the bibliographicCitation. https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/bibliographicCitation There is also a separate machine readable way to encode the data. See section 4: https://www.dublincore.org/specifications/dublin-core/dc-citation-guidelines/ All the best, -Hugh

…

Sent from my iPhone

On Thu, Jun 6, 2024 at 6:57 AM cetapslm ***@***.***> wrote: I'm new to DC Core. I would like to know what is the best term and descriptor for "place of publication" of a book. I also wonder if I can create qualifiers when needed. For example, dc.contributor.illustrator to state the name of a contributing illustrator of a book. Thank you in advance for you help. Luciano Moreira — Reply to this email directly, view it on GitHub <#128>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJ2JQ326NUNABKGAWJNEDZGBTFRAVCNFSM6AAAAABI4ZPYSKVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWG44DKOJVGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[cetapslm]

Hi Hugh,

Thank you so much! My context is that of a DSpace platform.

1. I read through the MARC roles. It seems good. Would it look like this then: dc.contributor.ill. Correct?
2. As for the publication, I understand your point. I can add it to bibliographicCitation. I did not understand, however, how to add the machine-readable way to encode the data in the context of the DSpace. Any suggestion?

Thank you so much for all the help; I'm really new to this and I'm struggling to make sense of it all.

Best wishes,

LM

[nishad]

@cetapslm Probably ongoing Dublin Core Scholarly Resources Application Profile (DC-SRAP) [1] work may be in the same direction.

[1] https://github.com/dcmi/dc-srap

[cetapslm]

Thank you so much, @nishad I'll follow the working group. Best wishes, LM

[HughP]

@cetapslm Re: 1. Yes that is how I have seen it serialized before. But there is no rule for syntax beyond "dc.contributor" it all depends on how the information is consumed by downstream information systems. Re: 2. I don't currently work with DSpace, but the value of BibliographicCitation would be the openURL syntax which is like the KEV syntax in the documentation. there is an NISO specification which explicitly explains the syntax. https://www.niso.org/publications/z3988-2004-r2010 I also find that Zotero has an exporter which works nicely.

…

On Fri, Jun 7, 2024 at 1:45 AM Luciano Moreira ***@***.***> wrote: Hi Hugh, Thank you so much! My context is that of a DSpace platform. 1. I read through the MARC roles. It seems good. Would it look like this then: dc.contributor.ill. Correct? 2. As for the publication, I understand your point. I can add it to bibliographicCitation. I did not understand, however, how to add the machine-readable way to encode the data in the context of the DSpace. Any suggestion? Thank you so much for all the help; I'm really new to this and I'm struggling to make sense of it all. Best wishes, LM — Reply to this email directly, view it on GitHub <#128 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJ2JRQIOYNXM53F3D2JBLZGFXL5AVCNFSM6AAAAABI4ZPYSKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TMOJZGI3DQ> . You are receiving this because you commented.Message ID: ***@***.***>

[cetapslm]

@HughP Thank you so much!