how are multiple links expected to present in json?
The current page scans field is just 1600 chars of text. So it is up to the uploader to format. The catalog 904 is the same, no imposed format. I don't know if the catalogers apply any formatting, I've asked Joyce.
Do you (@eshellman) have a preference? I've assumed the Wikipedia DB column should be the same as page scans, but it doesn't have to be. And I think 1600 is excessive, 400 should be enough.
The apps that show the field should apply a consistent format, with separators - semicolon, comma, LF, whatever.
https://github.com/gutenbergtools/ebookconverter/blob/master/ebookconverter/writers/SummaryWriter.py has code that reads and writes wikipedia links to the data base (in a 500 attribute with a specific string indicating it is a "wikipedia link about the book). We need to keep the storage the same. but when a dublin core object is read from the database, it should populate a wikipedia link attribute on the dublin core object. same when a metadata file is scanned. and when one or more wikipedia attributes are set on the object, in should get saved on the 500 attribute during the save of the dublin core object.
This will allow siimplification of the SummaryWriter object
how are multiple links expected to present in json?
The current page scans field is just 1600 chars of text. So it is up to the uploader to format. The catalog 904 is the same, no imposed format. I don't know if the catalogers apply any formatting, I've asked Joyce.
Do you (@eshellman) have a preference? I've assumed the Wikipedia DB column should be the same as page scans, but it doesn't have to be. And I think 1600 is excessive, 400 should be enough.
The apps that show the field should apply a consistent format, with separators - semicolon, comma, LF, whatever.
https://github.com/gutenbergtools/ebookconverter/blob/master/ebookconverter/writers/SummaryWriter.py has code that reads and writes wikipedia links to the data base (in a 500 attribute with a specific string indicating it is a "wikipedia link about the book). We need to keep the storage the same. but when a dublin core object is read from the database, it should populate a wikipedia link attribute on the dublin core object. same when a metadata file is scanned. and when one or more wikipedia attributes are set on the object, in should get saved on the 500 attribute during the save of the dublin core object.
This will allow siimplification of the SummaryWriter object