Skip to content

Commit

Permalink
Update 07-manipulating-MARC-data-advanced.md
Browse files Browse the repository at this point in the history
removed instructor notes
  • Loading branch information
jenmawe authored Sep 5, 2024
1 parent 019fab2 commit d51ebfe
Showing 1 changed file with 1 addition and 13 deletions.
14 changes: 1 addition & 13 deletions episodes/07-manipulating-MARC-data-advanced.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,6 @@ The Edit Shortcuts menu can be found by going to Edit in the menu in the MarcEdi
## Use Find or Find All to Verify Results
You can use Find or Find All to verify that the change did what you expected on your records in the file. If a result didn't work as expected, you can select "Special Undo". This is why it is important to profile your data before doing batch edits.

:::::::::::::::::::::::::::::::::::::: instructor

This is a good moment to review the [Profiling Your MARC data](https://librarycarpentry.org/lc-marcedit/05-profiling-your-MARC-data.html)

:::::::::::::::::::::::::::::::::::::::::::::::::

:::::::::::::::::::::::::::::::::::::::::


Expand Down Expand Up @@ -93,13 +87,7 @@ This is possible using the function called, Build New Field.
In the example above, if your 856 contains other subfields such as \$3, then these will not be retained because you are only building a new 856 that replaces the current one. To retain \$3 data, you would need to include this parameter in your function. This would look like `=856 40{856$3}\$uhttps://exampleproxy.edu/login?url={856$u}`

Also note, the build new field works on the first iteration of the field. When working in particular with the MARC field 856, if you need to build a new field using all of the MARC fields 856 in your record, you can use the syntax [x] as in {856$u[x]}. This will ensure all of the MARC fields in the records will undergo the build operation you specify.

:::::::::::::::::::::::::::::::::::::: instructor

This is a good time to re-iterate that MarcEdit has different ways to accomplish similar tasks. You can use Find All & Replace, Build New Field, or use the advanced subfield edit functions below. It's worth highlighting how these differ. In the example above, if there are records with the MARC field 856 that have a \$3 or other subfields besides \$u, then those subfields will not appear in the newly built MARC field 856. The Find All and Replace will only work on finding and replacing exactly what you entered in the Find All field. This is why it's important to profile data or use the Find All to review changes. For the Build New Field function, it is worth selecting the option to always create a new field and then check that new field to see if the build did what was expected. If it did, then you can use "Special Undo", and build the new field again with the option to "Replace Existing Field".

:::::::::::::::::::::::::::::::::::::::::::::::::


::::::::::::::::::::::::::::::::::::::::::::::::::


Expand Down

0 comments on commit d51ebfe

Please sign in to comment.