search

WGBH / PBCore2.0

Public Broadcasting Metadata Dictionary Project
http://www.pbcore.org
33 stars 9 forks source link

Attribute "@certainty" for pbcoreAssetDate #57

Open caseyedavis12 opened 10 years ago

caseyedavis12 commented 10 years ago

I suggest a new attribute for pbcoreAssetDate.

The @certainty attribute may be used to indicate the degree of precision in the dating, for example, "circa," "approximately," or "after." Then, we can refrain from including question marks in the value of the pbcoreAssetDate element.

awead commented 10 years ago

How do other cataloging schemas/standards approach this issue? Is this similar to any of them? Using circa or question marks, etc. is perfectly fine for some representations. If we choose to invent our own, that us sets apart from a standard practice and might make it difficult for future implementors.

One idea is to subclass the data into its known components, ex:

<pbcoreAssetDate>
  <pbcoreAssetYear>2008</pbcoreAssetYear>
  <pbcoreAssetMonth type="Gregorian">March</pbcoreAssetMonth>
  <pbcoreAssetMonth type="numeric">3</pbcoreAssetMonth>
</pbcoreAssetDate>

Which identifies only its known components and omits any unknowns. A bit pedantic, maybe.

caseyedavis12 commented 10 years ago

EAD also has the @certainty attribute for dates, but it does not have a controlled vocabulary for the attribute values.

From EADiva:

"CERTAINTY – not required. May be used to indicate degree of precision used in dating—”circa,” “approximately,” “after,” etc."

From: Adam Wead notifications@github.com<mailto:notifications@github.com> Reply-To: "WGBH/PBCore2.0" reply@reply.github.com<mailto:reply@reply.github.com> Date: Friday, August 1, 2014 10:56 AM To: "WGBH/PBCore2.0" PBCore2.0@noreply.github.com<mailto:PBCore2.0@noreply.github.com> Cc: Casey Davis casey_davis@wgbh.org<mailto:casey_davis@wgbh.org> Subject: Re: [PBCore2.0] Attribute "@certainty" for pbcoreAssetDate (#57)

How do other cataloging schemas/standards approach this issue? Is this similar to any of them? Using circa or question marks, etc. is perfectly fine for some representations. If we choose to invent our own, that us sets apart from a standard practice and might make it difficult for future implementors.

— Reply to this email directly or view it on GitHubhttps://github.com/WGBH/PBCore2.0/issues/57#issuecomment-50893757.

awead commented 10 years ago

OK. EAD borrowing is fine, then.

AllisonAnn commented 9 years ago

I'm transferring this issue to the spreadsheet, but wanted to add a comment about it. I guess I'll find out if comments is still open...

I've always assumed that pbcoreAssetDate mapped to DC Date - and for that reason, I've always maintained that the format for the date should be ISO 8601 (to conform to DC). With that said, whether or not @certainty is adopted for use with this element, I think that we should still encourage people to use ISO 8601 format, along with the LOC Extended Date/Time Format rules/suggestions for ISO dates. So, I think that the use of the question mark for an uncertain date should be retained, and suggested as best practice.

Maybe pbcoreCoverage would be a more effective place for an @certainty attribute?

kvanmalssen commented 9 years ago

Related to issue #58 and #80