openlibrary icon indicating copy to clipboard operation
openlibrary copied to clipboard

New edition contributor roles for LibriVox: book coordinator, meta coordinator, & proof listener

Open Freso opened this issue 1 year ago • 0 comments

Problem

A clear and concise description of what you want to happen

Add the roles “Book Coordinator”, “Meta Coordinator”, and “Proof Listener” to the options of contributor roles (potentially with “LibriVox” prepended).

Expected behaviour / screenshots (ex: Figma design screenshots for UI feature)

When editing an edition, it should be possible to add the LibriVox roles for Contributors.

Additional Context

example of the roles listed on the LibriVox book page

LibriVox has proof listeners who function much like proofreaders, book coordinators who [manage] all the other volunteers who will record chapters for a LibriVox recording, meta (or metadata) coordinators who help and advise Book Coordinators, and take over the files with the completed recordings ([…]). The files are then prepared and uploaded to the LibriVox catalogue, in a lengthy and cumbersome process. These roles are listed on LibriVox book pages, e.g., https://librivox.org/the-moon-endureth-tales-and-fancies-by-john-buchan/

These roles do not really have a proper equivalent in the current contributor roles (unlike readers/narrators and graphic designers) and as such there’s not currently a good structured way to add/store this data.

Proposal & Constraints

What is the proposed solution / implementation?

I suggest adding the following to the roles part of https://openlibrary.org/config/edition.yml (as of this writing starting on line 403):

- [LibriVox] Book Coordinator
- [LibriVox] Meta Coordinator
- Proof Listener

Note: Needs no code changes, just a site admin who can edit the infogami.

Is there a precedent of this approach succeeding elsewhere?

Seems to work fine for the other roles in the list :)

Which suggestions or requirements should be considered for how feature needs to appear or be implemented?

  • Should the coordinator roles be prefixed with “LibriVox” or not?
    • Doing this would make those roles very narrowly focused on LibriVox, but the roles might also not really be applicable to anything other than LibriVox (are there other LibriVox like projects following a similar workflow?).

Leads

Related files

https://openlibrary.org/config/edition.yml

Stakeholders

Note: Before making a new branch or updating an existing one, please ensure your branch is up to date.

Freso avatar Jun 18 '24 18:06 Freso