muscat
muscat copied to clipboard
rism-digital
🗂️ A Rails application for the inventory of handwritten and printed music scores
Lock the MARC field (110 $g) for cataloguers. Only editors shall have the right to make changes in this field. Thanks. Guido
If a Subject Heading is merged through the Subject Headings authority file, a duplicate 650 can potentially be created in the source record. Example: https://muscat.rism.info/admin/sources/1001037282/edit had both `Volkslied` and `Folk...
RISM beginners sometimes have trouble with the incipit numbers (031 $a-c). They might put all the numbers in $a (such as 1.1.1 or variations thereof) or maybe fill out only...
The `sources_to_institutions` table contains entries for source IDs that have been deleted or are no longer in Muscat. e.g., 402003050, 402004875, 402005008, etc. In theory, these records are the ones...
we have these sigla only for backward compatibility with some old catalogues, so it might be usefull to remove them from search and autocomplete. One idea is to mark them...
It is possible to put records in a folder that belong to both the cataloger's working group and an external working group, published or unpublished. Folder owners see a "publish"...
In the case something like #1233 repeats, send an error (to admin? email?) indicating the invalid user.
Currently, all terms entered into the field 650$a, whether in a Source record or in the Secondary Literature, end up in one index: https://muscat.rism.info/admin/standard_terms This is problematic for the users...
since {{brk}} was an intermediate local solution with Muscat (see #438). Maybe we can find a better replacement. Proposal is to some html-entity ` ` or ` `. Any more ideas?
To fix the extra places that are created as part of #1080 we should add the ability to merge Place records in the UI, if it is not already there.
Metadata
Owner
Metadata
🗂️ A Rails application for the inventory of handwritten and printed music scores