2022-04-18 meeting agenda and notes

Apr 18, 2022 3:00pm EDT / 2:00pm CDT / 1:00pm MDT / 12:00pm PDT

Attendees

@Rebecca Baugnon

@ebeckman (Unlicensed)

@Johanna Carll

@Jessica Crouch

@Regina Carra

@Margaret Kidd

Join Zoom Meeting
Meeting URL:	https://harvard.zoom.us/j/96512490463?pwd=RE5ZaDE0aGMzVkhtRklzUng5c2ttUT09&from=addon
Join by telephone (use any number to dial in)
Dial:	+1 929 436 2866 +1 301 715 8592 +1 312 626 6799 +1 669 900 6833 +1 253 215 8782 +1 346 248 7799
Meeting ID:	965 1249 0463
International numbers
One tap mobile:	+19294362866,,96512490463# US (New York)
Join by SIP conference room system
Meeting ID:	965 1249 0463
Password:	393020
SIP:	96512490463@zoomcrc.com

Agenda and notes

Agenda item	Item description	Notes

Agenda item	Item description	Notes
Welcome and check-in
Planning for next year	Start thinking about goals for next year. Membership changes.
Check in on ongoing work	Digital Object page review assignments have been added to User Manual Review Digital Object page review assignment check-in Look for place to record instructions for how to display a thumbnail in the PUI. Question: how best to link to data maps? Link to main page or to specific maps? Old business: Division between Creating and Managing Resource Records, Creating a Minimal Resource Record, and Adding Additional Information to a Resource Record No merge function, we don’t have delete permissions. UPDATE 4/3: updated page merging Creating and Managing Resource Records and Creating a Minimal Resource Record has been published (replacing Creating & Merging, to be renamed Creating Resource Records) .yml instructions in manual, found in https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/895812108 and https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/893976727 . The instructions verge into tech doc territory, but are more fleshed out than this page tech-docs . Need to indicate need sys admin permission, direct to tech doc
Rights statement documentation	Conversation on listserv. Do we need to say why you would use RS or is that up to repositories? Suggested additions to documentation from Kate Bowers: Do not confuse rights statements with conditions on access or conditions on use. Rights statements would rarely be applicable to a traditional (paper or mixed analog format) archival resource or accession. In practice, rights statements are overwhelmingly applied to single-level digital objects. An example of where it might be applicable at an aggregation level would be a set of digital files where you know each item has identical rights.
Other topics?