Overview metadata: use standardized terms or use what the archives/repo uses?

[johnjung]

Overview metadata: use standardized terms or use what the archives/repo uses?

[johnjung]

This transform "regularizes" a finding aid as I convert it to HTML. If you search through it for "ead:head", you'll see the headings I insert when one is not present for different elements.

Please feel free to review these- I can change them to whatever you'd like.

When a finding aid author has used a specific heading, my preference is to either respect the heading they used, or to treat it as a data issue and fix the heading in the EAD itself rather than to change explicit headings in the regularization step. If you'd like to talk through this please let me know, but my thinking here is that if we change elements behind the scenes we make it harder for finding aid authors to iteratively improve finding aids, since their editing software won't know anything about the substitution.

Please let me know what you think.

[johnjung]

After reading your issue again, I realized that the overview at the top of each finding aid, the elements inside the first did at the top of the archdesc, actually use label attributes, not headings. Please review the headings if you'd like, but for the specific issue you're describing, please search the stylesheet I linked above for "@Label" instead. (Let me know if we can talk through this one via Zoom.)

[MomoMoses]

for <physloc> let's use "Storage Location" -- I think it's clearer.

[MomoMoses]

ead:head for <accessrestrict> use "Conditions for Access" -- it's a more positive-sounding spin on the availability of the materials. Often the info here is that the collection is open for research!

ead:head for <altformavail> use "Alternative Form Available"

ead:head for <bioghist> use "Biography or History" - this way it covers both, we don't know in advance which one it is.

ead:head for <controlaccess> use "Indexed Terms"

ead:head for <fileplan> use "Filing System"

[MomoMoses]

Not sure it's necessary to have a heading for everything: <acqinfo> usually contains a sentence or two that are understandable without one. Let's see how it looks and revisit. Keep it for Phase One.

#PhaseTwo

[johnjung]

Please confirm: is this the complete list of headings to update, for now? (Once I update them I'll close this bug, but you can always re-open it.)

Also, should I override existing headings for these elements, like with <controlaccess>?

[MomoMoses]

This issue was just for the supplied headings where none exist. Exception was controlaccess

[MomoMoses]

So do not override these

[johnjung]

This is now fixed in dbb4456, and live on the server. I'm going to close this issue out, please re-open if necessary.