Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retain newline characters in Transcription display (old UMedia discards them, does not translate as <br> a la nl2br) #86

Open
mberkowski opened this issue Jun 8, 2023 · 2 comments
Assignees

Comments

@mberkowski
Copy link
Member

mberkowski commented Jun 8, 2023

Retain newline characters in Transcription display (old UMedia discards them, does not translate as
a la nl2br)

This might be merely a display issue where the view templates need to make <br> out of \n but it might also be that the indexer is discarding them via a filter in config/initializers/cdmdexer.yml

@mberkowski
Copy link
Member Author

@theberg75 As we've started to dive into this a little bit, I had thought we already had obvious examples where CONTENTdm had newlines in transcriptions that UMedia was throwing away, but looking over some items where I would expect to find line breaks in the transcriptions, they don't seem to be there in CONTENTdm's JSON.

https://server16022.contentdm.oclc.org/dmwebservices/index.php?q=dmGetItemInfo/p16022coll629/707/json
https://server16022.contentdm.oclc.org/dmwebservices/index.php?q=dmGetItemInfo/p16022coll621/143/json

Do you know of any items in CONTENTdm that do have newline \n characters encoded in the transcription?

@theberg75
Copy link

Not off the top of my head but I can dig around unless @jasonoroy - do you know of any?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants