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

<control>: express more adequately #23

Closed
1 of 9 tasks
SJagodzinski opened this issue Mar 20, 2017 · 3 comments
Closed
1 of 9 tasks

<control>: express more adequately #23

SJagodzinski opened this issue Mar 20, 2017 · 3 comments

Comments

@SJagodzinski
Copy link
Contributor

There is a need to express the <control> more adequately – we suggest the use or inclusion of similar fields within <eadheader> such a <descrules>.

[K. Cox]

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. [email protected] or [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
  • Suggestions for all Tag Libraries
  • Other

Wanted change/feature

There is a need to express the <control> more adequately – we suggest the use or inclusion of similar fields within <eadheader> such a <descrules>.

[K. Cox]

Context

This comment was part of the feedback from the staff in the Arrangement & Description Team at Alexander Turnbull Library (National Library of New Zealand) sent by Kirsty Cox.

@karinbredenberg
Copy link
Member

Consolidation with EAD

@ailie-s
Copy link

ailie-s commented Dec 23, 2019

Not sure whether this is a request to better describe the <control> element or to include more elements within <control>. Both <eadheader> and <descrules> have been omitted from EAD3, and <conventiondeclaration> (which is already in EAC-CPF) has replaced <descrules>.
We can certainly improve the description of <control> in the Tag Library based on EAD's description. More detailed examples of usage could be included in best practice guidelines.

@SAA-SDT SAA-SDT locked as resolved and limited conversation to collaborators Jan 30, 2020
@SJagodzinski
Copy link
Contributor Author

See solution in #81

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants