@status

[SJagodzinski]

Status

• add new optional attribute @status to <agencyCode>, <date>, <fromDate>, <nameEntry>, <otherAgencyCode>, <toDate> to indicate if an element contains the authorized or alternative form of a code or a name or to indicate unknown and ongoing dates
• values in limited to: authorized, alternative | unknown, ongoing

Creator of issue

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

Related issues / documents

New attribute @status #70 Topic_names_20200130.pdf Topic_dates_20200911.pdf

EAD3 Reconciliation

new EAC attribute

Context

new EAC attribute

Solution documentation:

Summary, Description and Usage and Attribute usage needed

May occur within: <agencyCode>, <fromDate>, <nameEntry>, <otherAgencyCode>, <toDate> Values:

• <agencyCode>, <nameEntry>, <otherAgencyCode>: authorized, alternative
• <fromDate> : unknown
• <toDate> : unknown, ongoing
• <date>: unknown

see also: Kerstins comment in #70:

@status on the other hand, qualifies - or categorises - the content of the according element.

• example needed
• Topic for Best Practise Guide

Example encoding

[SJagodzinski]

@ailie-s : Is <fromDate status="ongoing"/> useful?

[ailie-s]

@SJagodzinski : I don't think <fromDate status="ongoing"/> is useful.

[kerstarno]

Might be constructed, but in theory the following encoding would be valid, if we wanted to say that something has a timespan and that we know it's still active, but we are not sure about the actual start date:

<dateRange>
    <fromDate status="ongoing"/>
</dateRange>

Question might be - do we instead want to "enforce" an encoding such as:

<dateRange>
    <fromDate status="unknown"/>
    <toDate status="ongoing"/>
</dateRange>

by restricting the values for @status when used with <fromDate>?

[fordmadox]

We didn't discuss during today's meeting, did we? Anyhow, just let me know if I need to make any changes in the schemas.

[SJagodzinski]

Let's keep it simple:

Values:

• <agencyCode>, <nameEntry>, <otherAgencyCode>: authorized, alternative
• <fromDate> : unknown
• <toDate> : unknown, ongoing

[kerstarno]

I.e. @fordmadox - please remove "ongoing" as a possible value for @status with <fromDate>.

[fordmadox]

Update made (and this change does remove 'status' from the 'date' element, since those previously all got the same attribute definitions before..., see #179, so if we need to add that attribute back to 'date', let me know). See https://github.com/SAA-SDT/eac-cpf-schema/commit/8a9adea4a70b3f05632943865481df31bc53ec47

[ailie-s]

Tag Library Text:

Summary: Attribute that provides controlled terminology detailing the status of elements. Available in <agencyCode>, <fromDate>, <nameEntry>, <otherAgencyCode> and <toDate>. The terms available for @status are defined in closed lists that vary by element. Values: Values in <fromDate>: unknown Values in <agencyCode>, <nameEntry>, <otherAgencyCode>: alternative, authorized Values in <toDate>: ongoing, unknown

[kerstarno]

Tested as part of Schema Team's schema testing:

• @status is an optional attribute in (currently) <agencyCode>, <otherAgencyCode>, <nameEntry>, <fromDate>, and <toDate>
  • @ailie-s the TL draft above is missing <agencyCode> and <otherAgencyCode>
• Depending on its context, it can have the values "authorized" or "alternative" (<agencyCode>, <otherAgencyCode>, <nameEntry>), "unknown" (<fromDate>), and "unknown" or "oingoing" (<toDate>)
• Its data type is token

The above applies to both schemas, RNG and XSD.

[kerstarno]

There is currently a pending question if at least @status="unknown" should be re-instated with <date> in the same way as it's available with <fromDate>(see #179).

[SJagodzinski]

There is currently a pending question if at least @status="unknown" should be re-instated with <date> in the same way as it's available with <fromDate>(see #179).

Is it, cf comment and comment ?

[kerstarno]

Well, the question in #179 was pending.

Anyway, note taken for feedback on the call for comments. :-)

[kerstarno]

With the decision to not have @status="unknown" for <date>, this attribute is ready.

[kerstarno]

Following their meeting on 18 June, the EAD team would like to suggest that @status is added to <date> as well allowing the value "unknown" (i.e. the same as <fromDate>. The main use case behind this is the use of <date> as one of the possible sub-elements of <unitDateStructured>, where having an "unknown" status could help clarify cases of "no date"/"n.d." etc. which are relatively common when describing archival material.

[SJagodzinski]

EAC-CPF meeting 3 September 2021:

Decision: add the optional @status attribute to <date>, with a single option: “unknown”

[kerstarno]

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

I can confirm that @status with the (only) value "unknown" is now also available for <date> in both schemas.