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

@status #254

Closed
SJagodzinski opened this issue Jan 3, 2021 · 16 comments
Closed

@status #254

SJagodzinski opened this issue Jan 3, 2021 · 16 comments
Labels
Attribute Comments period issues to (re)discuss during the Call for Comments Tested by Schema Team Passed both the RNG and XSD schemas.

Comments

@SJagodzinski
Copy link
Contributor

SJagodzinski commented Jan 3, 2021

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. [email protected]

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
Copy link
Contributor Author

SJagodzinski commented Jan 3, 2021

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

@SJagodzinski SJagodzinski mentioned this issue Jan 3, 2021
9 tasks
@ailie-s
Copy link

ailie-s commented Jan 8, 2021

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

@kerstarno
Copy link
Contributor

kerstarno commented Jan 8, 2021

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
Copy link
Member

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
Copy link
Contributor Author

Let's keep it simple:

Values:

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

@kerstarno

This comment has been minimized.

@kerstarno kerstarno mentioned this issue Jan 12, 2021
@fordmadox

This comment has been minimized.

@ailie-s
Copy link

ailie-s commented Jan 19, 2021

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 kerstarno self-assigned this Jan 21, 2021
@kerstarno
Copy link
Contributor

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
Copy link
Contributor

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).

@kerstarno kerstarno added Tested by Schema Team Passed both the RNG and XSD schemas. Pending final decision labels Jan 21, 2021
@SJagodzinski
Copy link
Contributor Author

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
Copy link
Contributor

Well, the question in #179 was pending.

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

@kerstarno
Copy link
Contributor

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

@SJagodzinski SJagodzinski assigned SJagodzinski and unassigned ailie-s Mar 27, 2021
@kerstarno kerstarno added the Comments period issues to (re)discuss during the Call for Comments label Aug 4, 2021
@kerstarno
Copy link
Contributor

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
Copy link
Contributor Author

EAC-CPF meeting 3 September 2021:

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

@SJagodzinski SJagodzinski assigned ailie-s and fordmadox and unassigned SJagodzinski Sep 5, 2021
@SJagodzinski SJagodzinski modified the milestones: Tag Library, Schema Sep 5, 2021
@kerstarno kerstarno removed the Tested by Schema Team Passed both the RNG and XSD schemas. label Nov 2, 2021
@kerstarno
Copy link
Contributor

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.

@kerstarno kerstarno added the Tested by Schema Team Passed both the RNG and XSD schemas. label Jan 18, 2022
@SJagodzinski SJagodzinski removed this from the Schema milestone Jan 23, 2022
@SJagodzinski SJagodzinski removed their assignment May 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Attribute Comments period issues to (re)discuss during the Call for Comments Tested by Schema Team Passed both the RNG and XSD schemas.
Projects
None yet
Development

No branches or pull requests

4 participants