search

projectblacklight / arclight

A Rails engine supporting discovery of archival material
https://samvera.atlassian.net/wiki/spaces/samvera/pages/405211890/ArcLight
Other
39 stars 24 forks source link

Should we index and display <revisiondesc> ? #1454

Open marlo-longley opened 10 months ago

marlo-longley commented 10 months ago

It appears in the EAD header. We don't know if it is desired to display or if it's more of an internal thing for catalogers.

This ticket is broken out of https://github.com/projectblacklight/arclight/issues/898

gwiedeman commented 10 months ago

I would say yes as its transparency that's very useful for users. The ASpace PUI displays this.

Here is an example <revisiondesc>:

<revisiondesc>
    <change>
        <date>1989 July 10</date>
        <item>Encoded in EAD by Geoffrey P. Williams, Geoffrey A. Huth, and Salvatore Canino</item>
    </change>
    <change>
        <date>2001 April 17</date>
        <item>Updated by Lynn Dorwaldt</item>
    </change>
    <change>
        <date>2016</date>
        <item>Reprocessed and converted to EAD by Ben Covell</item>
    </change>
    <change>
        <date>2023</date>
        <item>Updated by Meghan Slaff</item>
    </change>
</revisiondesc>
mmmmcode commented 10 months ago

I've always viewed \<revisiondesc> as an internal change summary. If I'm interpreting the ead2002 tag library correctly, it is supposed to be used for tracking changes to the finding aid as an ead document, and not necessarily to the finding aid's intellectual content. There are other elements for tracking substantial changes to collection description or contents, like \<processinfo>, \<separatedmaterial>, etc. Interested to hear how other folks use it!

mmmmcode commented 10 months ago

@gwiedeman Hmm, I didn't know the ASpace PUI displayed it. I'm just thinking of all the revisiondesc notes that say stuff like "fixed typo", "revised note order", "updated repository information", etc., and whether that really matters to researchers. Maybe it can at least be something you have to click through to, rather than have front-and-center?

gwiedeman commented 10 months ago

Yeah, this has come up at TS-DACS with https://github.com/saa-ts-dacs/dacs/issues/70, as this should be more clearly defined and there's probably a ton of variation in practice. We often end up documenting reprocessing in both revisions and processing notes which is not great.

Also, the ASpace PUI displays it if its published. Though for ASpace workflows at least, if its not published it shouldn't export to the EAD.