Open mbjones opened 7 years ago
Original Redmine Comment Author Name: gastil gastil (gastil gastil) Original Date: 2012-06-07T20:15:31Z
List of xsl issues to fix or improve:
Categorized into (A) Missing content or functionality vs (B) Layout or labeling.
(A) Missing content or functionality
(B) Layout or labeling
de-couple the width of the physical description and other table-level eml display from the width of the table displaying attribute metadata. Often there are so many columns as to render the above
consider moving the table-level coverage and constraints to below the attribute information.
Table layout in methods sampling description: See for example knb-lter-gce.1.19 (inserted into demo2 as knb-test-gce.1.19). The text of the description gets smushed way over to the right column while the label "Description" takes up most of the page width.
"Number of Foot lines" to "Number of Footer lines".
entityName appears in html as if it were the entityLabel. Good to display both, but large/bold labeling one should be label. (in a
link to "Domain Info" change to "Allowed values and codes defined". This is per feedback from our data users who did not know what Domain Info was.
hide the xml download of the EML file at the bottom of the page. If someone knows to want it, they'll know to look for it. Too often, our data users think they're going to get a formatted-for-humans file.
hide
Original Redmine Comment Author Name: gastil gastil (gastil gastil) Original Date: 2012-06-07T22:31:25Z
Adding to the list, in category (A) Missing content or functionality
Original Redmine Comment Author Name: gastil gastil (gastil gastil) Original Date: 2012-06-10T01:16:16Z
another permutation on missing methods text... (A) Missing content or functionality
Original Redmine Comment Author Name: gastil gastil (gastil gastil) Original Date: 2012-06-14T01:12:39Z
Category (B) Layout or Labeling ... though a rather embarrassing one.
See for example https://demo2.test.dataone.org/knb/metacat/knb-test-mcm.58.4/default I looked in the EML doc and there is nothing repeated there.
The abstract/section/para/literalLayout is repeated in the html. The intellectualRights/section/para/itemizedlist/listitem/para/literalLayout are all repeated But the methodStep/description/para/literalLayout are NOT repeated
It only gets repeated when the literalLayout is under a section.
A good reason for stalling on fixing that one is that a lot of existing EML in the LTER catalog still uses literalLayout when pre is NOT intended, due to not understanding its purpose. That is gradually getting fixed. So, just as well that the skins not fix this just yet. Unfortunately, there is also some EML which is using literalLayout as intended, and that isnt getting rendered properly yet.
Original Redmine Comment Author Name: gastil gastil (gastil gastil) Original Date: 2012-06-14T01:16:08Z
Actually, in the intel rights of that example https://demo2.test.dataone.org/knb/metacat/knb-test-mcm.58.4/default
the text gets repeated THREE times: twice as para and then a third time all concatenated together as if there were no listitem nor para tags.
Original Redmine Comment Author Name: Margaret O'Brien (Margaret O'Brien) Original Date: 2012-06-28T22:38:30Z
Two SBC LTER datasets, when viewed through the LTER skins yield a blank page:
This does not happen through the KNB skins, but I thought were the same as what LTER used. So this might not be a general bug. http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=knb&docid=knb-lter-sbc.44
These 2 datasets are EML 2.1, and have inline data in a CDATA section.
Original Redmine Comment Author Name: Redmine Admin (Redmine Admin) Original Date: 2013-03-27T21:31:05Z
Original Bugzilla ID was 5615
Author Name: Margaret O'Brien (Margaret O'Brien) Original Redmine Issue: 5615, https://projects.ecoinformatics.org/ecoinfo/issues/5615 Original Date: 2012-06-05 Original Assignee: Margaret O'Brien
examine EML default HTML-skins to make sure that they reflect good EML practice, and that labels and layout are intuitive to non-developers. This is especially important so that EML will reflect positively on applications which present it, like Metacat.