Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion to add <title> to EAC-CPF #60

Open
4 of 9 tasks
kerstarno opened this issue Feb 26, 2019 · 3 comments
Open
4 of 9 tasks

Suggestion to add <title> to EAC-CPF #60

kerstarno opened this issue Feb 26, 2019 · 3 comments

Comments

@kerstarno
Copy link
Contributor

kerstarno commented Feb 26, 2019

Creator of issue

  1. Kerstin Arnold
  2. TS-EAS member; here: representing the Shared schema subteam
  3. easiest to reach via email: [email protected]

The issue relates to

  • EAC-CPF schema issue
  • EAC-CPF Tag Library issue
  • EAD schema issue
  • EAD Tag Library issue
  • Schema issue
  • Tag Library issue
  • Suggestions for all schemas (potentially)
  • Suggestions for all Tag Libraries (potentially)
  • Other

Wanted change/feature

  • Text:
    The Shared schema team is currently reviewing differences and similarities between EAC-CPF and EAD3 in order to identify potential for creating a shared schema and to understand the implications of such endeavour.
    During our conversations, we've come across the element <title>, which currently is only available in EAD, but not in EAC-CPF. There are, however, use cases in the community, where other elements have been used with @localType="title" in order to compensate the lack of a dedicated element (e.g. <span localType="title">).
    We would therefore want to suggest considering to add <title>to EAC-CPF. Context of usage could be e.g.
  • <biogHist> with its subelements <abstract>, <citation> and <p>,
  • <citation> in other contexts,
  • <p> in other contexts,
  • <event>,
  • <item>
  • <relationEntry> as subelement of <resourceRelation> (or rather <title> as direct subelement of <resourceRelation>)
@SJagodzinski
Copy link
Contributor

@kerstarno : is this related to #51 ?

@kerstarno
Copy link
Contributor Author

kerstarno commented Feb 27, 2019

@SJagodzinski: I wouldn't say that it is. #51 is very much about formatting, as far as I understand the initial request - and when leaving aside the more conceptual aspects of that issue.

This issue here might have a formatting aspect to it, but its main driver is retrieval of information pertaining to an intellectual work, such as a monograph, serial, or painting, created by or related to the entity described.

E.g. if you'd describe a writer/author/playwright/journalist/academic with EAC-CPF, you might want to include some of her/his most commonly known or most influential pieces of work. If you had the possibility to do that with a dedicated <title> element rather than having it as part of a longer piece of text in - let's say - a <p> or <abstract>, you might e.g. be able to create a "list of publications" based on the encoding with <title>.

@SJagodzinski
Copy link
Contributor

see also comparison report

This was referenced Jan 21, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants