Skip to content

In Episode 3, Working with MARC files: #201

@jenmawe

Description

@jenmawe

How could the content be improved?

For the Character Encoding callout in Working with MARC files, I wonder if it would be useful to give a brief definition of what character encoding is in case people don't know, either in the callout or the glossary - the link did not quite explain it either.

In the MARC File Types callout:
Table row 4 has "UTF8" when previous text has been "UTF-8" - probably best to be consistent
In row 5, it looks like the intention for the bit "eXtensible Markup format" is to show what XML stands for, but it doesn't include the Language for L
The bottom text of the callout says the file needs to be in mnemonic format and that binary must be converted - perhaps it might be good for clarification to say something like "...your file needs to be in MARC mnemonic format (mrk). If you only have a binary file (.mrc)..."
In the MARC Tools section:
The capitalisation of "eXtensible" before the Character Encoding callout reads a bit awkwardly. I think it should be okay to leave it uncapitalised
In the callout, there is a "MarEditor" typo, and also a missing full stop at the end
In the Break a MARC Binary File checklist, it might be useful to give specific information re: teh sample file - e.g. the file name for poitn 3 and the number of expected processed records for point 7
In the MARC Record layout section:
A typo in the MARC Syntax callout: "preceeding" should probably be "preceding" - but "before" might be better
In the Setting MarcEditor Preferences section:
This sentence from the start of the second para feels awkward: "Within the MarcEditor preferences, you can adjust the font and font size within the MarcEditor."
For the Behavior When You Reset Your Preferences callout, is the popup window having a chance to close due to a bug? Might be worth making it clear if so
For the Key Points, the "allow" in the second point should be "allows"
For the Key Points, points 3 and 4 overlap a little and could either be collapsed into one point or point 4 could be trimmed a bit

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions