https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39418

            Bug ID: 39418
           Summary: RDA Carrier, Content, & Media Vocabularies
 Change sponsored?: ---
           Product: Koha
           Version: Main
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Cataloging
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected]

On our Koha, we've loaded the RDA vocabularies for MARC 336 Content, 337 Media,
and 338 Carrier into our authorized values in order to connect them with the $a
and $b subfields of those fields in our MARC frameworks. This bug would preload
these vocabularies for new instances of Koha.

There are two AV categories per field, one for the human-readable term ($a) and
one for a short code ($b). I made the lib/lib_opac text for the codes the term
they represent, so one does not have to memorize the meanings of the codes.

I do not see any instance of an authorized value being connected with a MARC
field during installation (looking in
installer/data/mysql/en/marcflavour/marc21/mandatory/marc21_framework_DEFAULT.yml
where all the authorised_value properties are empty) so I have not done so with
these either. That seems reasonable; some libraries may want to use different
terms. But the RDA vocabs are widely used and stable, so including them as an
option for catalogers is worthwhile.

To load these into an existing Koha instance, this is the SQL we used:
https://github.com/phette23/scrape_rda_vocabs/blob/main/koha.sql

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to