more seed data for MARC21 fixed field values would be nice

Bug #1306258 reported by Galen Charlton on 2014-04-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

The patches for bug 1272074 introduce the ability to populate fixed field values in the MARC editor using a context menu.

The ability to do this for a given fixed field position(s) is dependent on several bits of configuration data, including:

- config.record_attr_definition
- config.coded_value_map

Seed data for crad exists for most, but not all of the fixed field positions supported by the MARC editor. Exceptions include Srce (cataloging source) and Cont (nature of contents).

However, rather more fixed field positions lack ccvm seed data. Examples include:

Alph
Elvl
Ctrl
Conf
Biog
MRec
Ctry
GPub
Indx
Desc
Ills
Fest
DtSt

Since all of these field positions have value lists that are set by the MARC21 standard, providing more seed data would spare users from having to manually enter values that change rarely and don't often get customized.

Evergreen master

Revision history for this message
Galen Charlton (gmc) wrote :

The branch collab/gmcharlt/lp1306258_seed_data_for_fixed_fields of the working/Evergreen repository contains work in progress. At present seed data for various MARC21 008 field positions is now available, provided by a utility I wrote that parses a file used by the Koha project to store such information.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1306258_seed_data_for_fixed_fields

Changed in evergreen:
importance: Undecided → Wishlist
Revision history for this message
Galen Charlton (gmc) wrote :

As Dan Scott points out, https://github.com/internetarchive/openlibrary/issues/15 implies that the rate limit has been removed (though the API documentation has not been updated to reflect that).

Revision history for this message
Galen Charlton (gmc) wrote :

Comment above is for a different bug, sorry.

Revision history for this message
Ben Shum (bshum) wrote :

Figure this will be something we plan to fix by 2.7, adding initial review target, but will followup on content to get this pullrequest ready.

Changed in evergreen:
milestone: none → 2.next
status: New → Triaged
Revision history for this message
Remington Steed (rjs7) wrote :

Looks like this bug was solved by bug 1371647.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers