Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Rebecca Baugnon

ebeckman (Unlicensed) (absent)

Johanna Carll

Jessica Crouch

Regina Carra (absent)

Margaret Kidd (regrets)

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 item

Item description

Notes

Welcome and check-in

Planning for next year

Start thinking about goals for next year. Membership changes.

Possible goals:

  • Restructure page watching assignments to be compatible with membership fluctuations

  • Develop an onboarding workflow and create documentation on what to share with new members

Check in on ongoing work

Old business:

Better to link to AS website maps than GitHub because Lyrasis/AS team has more control over the pages

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?

Planned development freeze on June 3rd. Features will be turned over for testing and documentation soon after. Anticipated changes to spawning and preferences (global, repository, user). Inclusive examples work expected to be complete at end of month, so hopefully data will be in place for documentation updates related to next release. There will be a dedicated instance for user documentation.