acq: Identifier field maps to undefined subfield
Bug #1959616 reported by
Andrea Neiman
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
New
|
Undecided
|
Unassigned | ||
Bug Description
This is an extant bug that was uncovered in the Angularization of the Purchase Order & Line Items interfaces
When creating a Brief Record, some of the fields in the form map to specific MARC fields & subfields.
However, the Identifier field attempts to create the following (where '123' is the Identifier value):
001 __ $undefined 123
In the old Dojo interface, the Brief Record is happily created with an undefined subfield, though I imagine that might cause problems down the line.
In the updated Angular interface, the Brief Record will not be created if there is any input in the Identifier field. This fails silently to the user but noisily in the console.
| description: | updated |
Revision history for this message
| Jennifer Pringle (jpringle-u) wrote | #1 |
To post a comment you must log in.
I'm not sure that the Identifier field should be a field in the acq Brief Record form.
When you create a new record using "Cataloguing -> Create New MARC Record" Evergreen automatically adds the 001 field when you save the record. Possibly acq should just let Evergreen do this when the records are loaded into the catalogue rather than letting staff manually enter a value.