Page History

Include Page

	Meeting Notes (navigation) - Best Practices for Authoritative Data Working Group (C2)
	Meeting Notes (navigation) - Best Practices for Authoritative Data Working Group (C2)

Expand

title	Table of Content

Table of Contents

maxLevel	3

ACTION ITEMS:

First, Next, Previous, Last: https://github.com/LD4/entity_metadata_management/pull/62
Provides flexibility between using a json object vs. a URL
Provides definition of Next and Previous with Next being a must and Previous is optional
Order Preference: https://github.com/LD4/entity_metadata_management/pull/16

Inconsistency with Deprecate: https://github.com/LD4/entity_metadata_management/issues/53 (see notes from last meeting, 2022-09-12 Meeting: Continue to Review Document).
Add vs. Create https://github.com/LD4/entity_metadata_management/issues/32
Add, update, remove relate to the "scheme" or collection. Remove does not mean disappear, i.e. it is deprecated, not deleted
Nancy F: what if you change an old term to a new term?
Kevin: In LCSH, LC would deprecate the old lccn and add a new lccn for the new term, with a pointer from the old to the new. Name is different. The old can remain valid if it is a name change
Date properties: https://github.com/LD4/entity_metadata_management/issues/39
Kevin: use "published" for the publication of the notification (e.g. for LCSH it is weekly), and "update" as the type of date of when the object was updated. LC activity stream is not currently doing that, and it would be hard to change, but that's what Kevin thinks they should be
All: please read and comment on the date issue (#39)

Vitus Tang

Kevin Ford

Nancy Falgren

Dave Eichmann