Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeline for PAE2 #129

Open
ahankinson opened this issue Jun 3, 2024 · 7 comments
Open

Timeline for PAE2 #129

ahankinson opened this issue Jun 3, 2024 · 7 comments
Labels
Audience: RISM internal Issues that affect RISM staff Type: Spec Administration Changes to processes or external factors
Projects

Comments

@ahankinson
Copy link
Contributor

Request for Comments:

A possible 2-year timeline for the introduction of PAE2.

  • 2024: Presentation at IAML, finalize spec
  • 2024-2025: Write Guidelines, other documents, website, etc.
  • 2025: Circulate spec and guidelines widely for comments; begin initial talks with vendors, MARC21/UNIMARC, IAML/IFLA etc.
  • 2025-2026: Review and address comments, update tooling; preliminary tests for upgrading existing incipits.
  • 2026: Finalize documentation and website, Release V2; update Muscat; Roll out upgraded incipits

Questions:

  • Timeline: too long? too short?
  • Any major headings that are missing? Education / Training?
@ahankinson ahankinson added Audience: RISM internal Issues that affect RISM staff Type: Spec Administration Changes to processes or external factors labels Jun 3, 2024
@lpugin
Copy link
Contributor

lpugin commented Jun 4, 2024

Looks good. I don't think it is too short.

Depending on the feedback, we will need to see how to organise the transition in Muscat, which might include a V1 deprecation phase where cataloguers might still be able to enter incipits in V1. But this is a separate timeline, I think.

@jenniferward
Copy link
Collaborator

Koha (https://koha-community.org/) is the only other major community that uses Plaine & Eaise that I know of. They introduced incipits maybe 2-3 years ago, following PAE. It would be good to touch base with them at some point for them to update their documentation, but also to maybe collaborate on training, and maybe they have some input from their side.

We definitely need training/workshops for our users, but I think a general workshop for non-RISM people would be useful as a PR gesture but also to offer something of general interest to the musicology/cataloging/MIR etc. community. Maybe we can do webinars with IFLA, IAML, and other groups.

@BaMikusi
Copy link
Collaborator

BaMikusi commented Jun 4, 2024

Personal communication in workshops is fine, but if we are talking of many people -- and, by our standards, all active Muscat catalogers should already be a substantial group -- I wonder if it would not be worthwhile to produce an online tutorial specifically focusing on the aspects that change with V2. I am guessing such a tutorial should not be too difficcult to create (the MEI community for one certainly seeks to give the impression that it's an easy go: https://music-encoding.org/tutorials/199-writing-tutorials.html), and could then be used not only by catalogers a couple of times before going back to Muscat 'live', but also (with some points added) by newcomers. In the longer run, arguably less work than holding an endless series of workshops.

@jenniferward
Copy link
Collaborator

It might be helpful to organize a presentation with the IAML Online Events Committee to benefit those who won't be able to travel to Stellenbosch.

@jenniferward
Copy link
Collaborator

Have you thought about translations? Some bits of PAE are already in the Muscat languages thanks to our guidelines. I bet some of our translators would be willing to contribute to it.

@BaMikusi
Copy link
Collaborator

BaMikusi commented Jun 7, 2024

Whereby for the actual effect it might be more important to have the Guidelines available also in other languages, so -- if there is limited capacity for translations -- perhaps the latter should be prioritized?

@ahankinson
Copy link
Contributor Author

Good point!

I think the guidelines would have priority, but it would be appropriate to explore this further. I've created #133 to track this specifically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Audience: RISM internal Issues that affect RISM staff Type: Spec Administration Changes to processes or external factors
Projects
PAE2
Awaiting triage
Development

No branches or pull requests

4 participants