Free Text Option in Leap MARC Editor
Add an optional free-text MARC editing mode to the Leap MARC editor that allows professional catalogers to directly edit bibliographic fields as plain text. Ideally, this would be toggleable at the record level, allowing staff to switch between the formatted MARC view and freetext view as needed.
Leap's current MARC editor is great for copy cataloging, minimal edits, or non-professional staff. However, full-time professional catalogers are often frustrated by the inability to update multiple field at once, paste long blocks of MARC data or navigate through tags using the keyboard. For this type of workflow, Leap's editor is signficantly slower and more cumbersome than the free-text editor in the Client
This enhancement would add a toggleable "Freetext view" within the existing Leap MARC editor. The default view would remain the structured MARC editor, but catalogers could toggle a record into freetext mode, make changes as needed, then toggle back. This preserves Leap's accessibility for non-professional staff while adding in functionality for power users.
For the sake of an example, I vibe-coded a quick demo of what this could look like - https://pinnaclelibraries.org/leapmarcdemo - The default view is still Leap's "table-like" structure, but the toggle at the top allows the user to switch to a freetext editor. Catalogers can make their edits then toggle back to the structured view before saving.
-
Wes Osborn
commented
Also, I would caution about leaving the current field by field editor the default. I think that should be a user toggle option as to which one opens up when you go to edit a record.
-
Wes Osborn
commented
If you want people to edit MARC records more in Leap, you're gonna need something like this. I wonder what happens when people bork the record by leaving out a space or something in a fixed field.
This would likely make it easier to support things like undos since that is built in to most web browsers in free text fields.
I don't think it has to be permissioned on our end, there are so few people editing MARC records and those who don't feel comfortable with something like this are unlikely to use it. I suppose a middle ground option would be an enable/disable at a branch level to give you some degree of control.
-
Lynn Reynish
commented
I can definitely see the benefit to this but I would also prefer to see this permission controlled if at all possible.
-
Eric Young
commented
I want this with permission controls on who can toggle into this awesome power/advanced editor.