Replace curly braces {{brk}} with something else

[HirschSt]

since {{brk}} was an intermediate local solution with Muscat (see #438). Maybe we can find a better replacement.

Proposal is to some html-entity 
 or 
. Any more ideas?

[jenniferward]

Is data exchange a concern, particularly those who might encounter in a non-browser environment?

[fjorba]

May I suggest the plain old \n? So \n\n would be <p> and\n, <br>.

The advangatge is that both conventions do not overlap. <tag> has no possible syntax conflict with \x, and vice-versa. At the same time, \n is mostly universally understood, not only for the computer-literate people, but also for any person that has worked along with programmers, or has had any exposure to computer tech documents.

[HirschSt]

End of line (probably both with Line Feed and Carriage return) with Marc21 in Muscat unfortunately has a different meaning, see https://github.com/rism-ch/muscat/blob/09380dc808937949574179ecb2b609ebc0962d67/lib/marc.rb#L114, so replacing with \n is not possible IMO

[HirschSt]

Internally it would be replaced, see https://github.com/rism-ch/muscat/blob/09380dc808937949574179ecb2b609ebc0962d67/lib/marc_node.rb#L616

[HirschSt]

@fjorba nevertheless thanks for this proposal

[fjorba]

I see. What about vertical bar (|), maybe escaped (\|) or doubled (||) if needed for the parser? It is hardly used in text, it is easy to type, it has a visual appeal, and it is sometimes used when quoting poetry for a new line.

[xhero]

I think we use the | for line breaks in diplomatic transcriptions, @jenniferward ? or is it / ? Where does the {{brk}} happen? in transcriptions or comments?

[jenniferward]

We use | for line breaks in diplomatic transcriptions. {{brk}} happens in about 10 fields, basically wherever the was opportunity (even 852 shelfmark, but I fixed that). The examples here show every field where it comes up: https://muscat.rism.info/admin/folders/455

[jenniferward]

{{brk}} is used in 4 fields (based on OPAC data dump, June 2020): 031$q: ca. 890x (Edit: Maybe more like 450) 245$a: ca. 10,000x 500$a: ca. 8,500x 563$a: ca. 438x

031 and 563 can probably safely be moved to repeated instances of the field. I will look at that this week, then we can look at the more difficult fields later.

[jenniferward]

563$a: I took a look at the records with {{brk}} in 563. I think it would be safe to split it into multiple 563s: a new 563 for each {{brk}}. Some records use multiple 563s as well as brk (https://muscat.rism.info/admin/sources/467020001). Some records have up to maybe 4 instances of brk. But I don't see any records where multiple notes would be a problem.

031$q I also looked at the records with {{brk}} in the 031$q. It is clear that multiple notes are intended here. Some records have multiple incipits, each with multiple brks per incipit: https://muscat.rism.info/admin/sources/211007215 https://muscat.rism.info/admin/sources/211007215 Most of the records seem to have 5 brks or less, though.

[lpugin]

I agree with @jenniferward that {{brk}} in 245 do not really make sense. Splitting them into one 245 and additional 246 looks like a proper way to fix them.