Table of Contents formating improvements

[patrickzurek]

JIRA issue created by: rcook Originally opened: 2012-05-16 12:12 PM

Issue body:

Below was Reported by Mike Bell 5/16/2012. Jennifer and [~mwesley] - thoughts on this? What can be done? CC too [~dlindahl]

I noticed that the table of contents does not have any formatting breaks in it, the lines all just stack together. In Voyager, there are
's between each item in the TOC in the brief view, and there are MARC (subtags?) in the staff view. i.e., in the 505 00 field, each number has a |g in front of it, and each name has a |t in front of it. I guess they get stripped out in process of being harvested or digested into XC.

This issue has attachments associated with it (external link): toc.png toc2.png toc3.png

[patrickzurek]

JIRA Comment by user: pkiraly JIRA Timestamp: 2012-05-18 02:43 AM

Comment body:

Randall, it is an MST problem. We can not handle it in Drupal, since in Drupal it is already converted before we harvest them.

[patrickzurek]

JIRA Comment by user: rcook JIRA Timestamp: 2012-05-21 04:12 PM

Comment body:

Below is the MST MARC XML

/marc:datafield

The Limits of Science --/marc:subfield Metascience --/marc:subfield Science and Magic --/marc:subfield The Magical Theory of Everything --/marc:subfield The Music of the Spheres --/marc:subfield Science and Mathematics --/marc:subfield Numbers --/marc:subfield Quantum Magic --/marc:subfield Science and the Mind --/marc:subfield Science and Society --/marc:subfield Science and Art --/marc:subfield Science and Sensibility./marc:subfield /marc:datafield And they get turned into this: dcterms:tableOfContentsThe Limits of Science -- Metascience -- Science and Magic -- The Magical Theory of Everything -- The Music of the Spheres -- Science and Mathematics -- Numbers -- Quantum Magic -- Science and the Mind -- Science and Society -- Science and Art -- Science and Sensibility./dcterms:tableOfContents While in marc, they are separate, each with their won code "t". Why can't we "mush" them into the dcterms in a more useful and meaningful way? [~jbowen]

[patrickzurek]

JIRA Comment by user: pkiraly JIRA Timestamp: 2012-05-22 11:15 AM

Comment body:

Jennifer, is it possible to use a more technical type separator, which possibly can not appear in the text? I mean: I guess it would be a totally possible case a subtitle might be: "Science and Mathematics – Numbers". In this case we can not use hypens as separator, because it will break the one subtitle into two subtitles. We might use an XML separator, but it can be problematic in parser side. We might use SPACE + HYPEN + HYPEN + HYPEN + SPACE as separator, because existing of 3 hypens in a row is quite unrealitic in real TOCs.

To have such a separator is important, because that way we can create a real list from a single text, and we can format is as Randall suggest or any other way a list can be formatted. Without such a separator we can easily create errors when we creates the lists.

[patrickzurek]

JIRA Comment by user: jbowen JIRA Timestamp: 2012-05-29 04:21 PM

Comment body:

A bit more info on what the data is going to be like in the original MARC records: standard ISBD punctuation has the space+hyphen+hyphen+space between each title. I believe that Voyager simply looks for those characters and puts in a line break when it finds that. Peter or MT, can't we simply do the same thing in Drupal for the Table of Contents field? It looks like our transformation is maintaining that punctuation (as it should). Some MARC records will have the extra subfielding and some won't - older records will not have it so I don't see that it would be worthwhile trying to do something elaborate with it. Using the punctuation to determine the line breaks is going to be imperfect too, but it should end up working as well in XC as it does in Voyager.

[patrickzurek]

JIRA Comment by user: mwesley JIRA Timestamp: 2012-06-05 03:23 AM

Comment body:

I added line breaks so that it looks like Voyager. This is a very simple fix (1 line of code and 2 minutes work), so we can change as appropriate if it doesn't work in all situations.

[patrickzurek]

Issue resolved: 2012-06-05 03:23 AM