search

SAA-SDT / eac-cpf-schema

https://eac.staatsbibliothek-berlin.de/
10 stars 4 forks source link

@detailLevel #274

Closed SJagodzinski closed 2 years ago

SJagodzinski commented 3 years ago

Level of detail

Creator of issue

  1. Silke Jagodzinski
  2. TS-EAS: EAC-CPF subgroup
  3. silkejagodzinski@gmail.com

Related issues / documents

Why not make "level of detail" an authorized attribute again? #226

EAD3 Reconciliation

new EAC attribute

Context

Solution documentation:

Summary needed

Optional within: <control> Values: minimal, basic, extented

Example encoding

fordmadox commented 3 years ago

The new branch is ready for testing: https://github.com/SAA-SDT/eac-cpf-schema/tree/issue/226

fordmadox commented 3 years ago

This can also be tested in our regular development branch, as well.

kerstarno commented 2 years ago

As a note: The EAD team discussed this during their meeting on 17 September and the general feedback has been that we need to make sure we can describe and explain the use cases for the attribute and its three possible values sufficiently and clearly. There especially were concerns with regard to the question whether the level of detail refers to the descriptive data provided in the EAS file or to the way the information is encoded.

Furthermore, the EAD team will check against DACS and MARC to review the terms used there and to potentially come up with mappings for these terms (https://saa-ts-dacs.github.io/dacs/08_part_II/06_chapter_13/05_level_of_detail.html and https://www.loc.gov/marc/bibliographic/bdleader.html (17 - Encoding level)). This will be picked up again during the next EAD team meeting on 15 October. Should this have any impact on the terms used as values for this new attribute, the EAD team will provide according feedback in this issue.

kerstarno commented 2 years ago

Following up from my previous comment: The EAD team discussed the addition of @detailLevel again during their meeting on 15 October and also looked at values uses in DACS and MARC. Reviewing the options available, the EAD team agrees with the suggested values "minimal", "basic", and "extended" and will work on a mapping suggestion towards the values of DACS and MARC, which could become part of the Best Practices Guide.

kerstarno commented 2 years ago

Re-tested with the XSD and RNG schemas available in the development branch (status of 8 January 2022).

I can confirm that @detailLevel is now available as optional attribute of <control> in both schemas and can have the values "minimal", "basic", or "extended".