Bug 27176 - With Advanced Editor if fields are out of order, they also display out of order
Summary: With Advanced Editor if fields are out of order, they also display out of order
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 33650 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-12-08 22:33 UTC by Kelly McElligott
Modified: 2024-04-05 22:48 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly McElligott 2020-12-08 22:33:44 UTC
When a library uses the z39.50 search through the Advanced editor and imports a record that has marc fields out of order, such as having a 700 field listed first, followed by the 245, then the 008.

Importing this record will display the fields out of order in the advanced editor.  There is no easy way to re-order these fields in the advanced editor module, but it can be done through the clipboard. 

Using the basic editor, importing the same file with fields out of order will import correctly.  If this record is saved, and then re-opened in the Advanced Editor, the fields are ordered correctly. 

It would be convenient and consistent to have fields ordered when importing a record through both the advanced editor and the basic editor. 

A workaround to the library that has imported (through the Advanced Editor) one of these records that have marc fields out of order.  Once this record has been saved to Koha, reopened in the Basic Editor, and then opened through the Advanced Editor- the fields will be in the correct order.
Comment 1 Katrin Fischer 2023-07-01 14:40:19 UTC
Hi Kelly, do you have a target where such records could be found for testing?
Comment 2 Phil Ringnalda 2023-07-03 18:46:24 UTC
An inconvient one for testing since it requires an account, but useful for showing the reason I disagree with fixing this bug: OCLC records are typically ordered like

600 _ 0 $aName
650 _ 0 $aTopic
650 _ 1 $Simpler
600 _ 7 $aName$2fast
650 _ 7 $aTopic$2fast
600 _ 7 $aName$2sears
650 _ 7 $aSemi-simpler$2sears

making it simple in the advanced editor to get to the end of the ones you want and then just delete delete delete. Unless someone saved the record in the basic editor before you got to it, when you have to go through each type of subject tag picking out the ones you don't want.

But just to see that it happens, Library of Congress - they put 906/925/955 before 010.
Comment 3 Phil Ringnalda 2024-04-05 22:48:02 UTC
And it's not specific to z39.50. If you intentionally put your notes in the order

520
505
511
500
500
500

they will stay that way, and will be displayed that way in the staff and OPAC notes tabs, unless someone comes along and saves your record in the basic editor, which will put the 500 "Series number from goodreads.com" above the summary and the contents notes.
Comment 4 Phil Ringnalda 2024-04-05 22:48:24 UTC
*** Bug 33650 has been marked as a duplicate of this bug. ***