[GeoNetwork-devel] [GeoNetwork opensource Developer website] #290: PDF "printed" metadata

#290: PDF "printed" metadata
------------------------+---------------------------------------------------
Reporter: osjonathan | Owner: geonetwork-devel@…
     Type: defect | Status: new
Priority: minor | Milestone: v2.6.0 RC2
Component: General | Version: v2.6.0RC1
Keywords: |
------------------------+---------------------------------------------------
A few minor issues with exported PDF's, a mixture of bugs and suggestions.
Attached is an export PDF from our test dataset.

a) Very trivial thing. if you look in the attached pdf export you'll see
an extra space leading the comma between the "theme" keywords and the
"place" keywords giving " , " (sans quotes). Maybe separate different
themes by semi-colon in the export? Examples:
Water, rain, precipitation , earth, warwickshire
fairies, pixies, magic folk, stuff , World, wcc, tree stumps

b) A suggestion - put the page number and current text header at the
bottom of the page - might want to split them up too so the page num is to
the bottom right, while the date and "geonetwork opensource" are to the
bottom left.

c) The metadata doesn't use the entire width of the page, only about 75%
of the main body width.

d) The "Keywords :" column is in italics, is this intentional? If so, may
I suggest only have the data itself be in italics, and not the "Keywords
:" part of the line.

e) There's a colon leading the unique identifier but no lead-in-text
(i.e., should probably be "Unique ID :"

f) "Aggregate Results matching search criteria :1" - that's meaningless in
it's current context because anyone you send the document to won't know
what the "search criteria" were. Either include all search parameters or
change the line to something mroe generic

g) There's no indication as to where the data is from other than a
GeoNetwork install. I'd suggest including a heading to the document,
probably including site name & organisation (from the system
configuration), and the URL.

h) A little more vertical space between each metadata item (i.e. where the
thick <hr> element is, a little more space to the top and bottom of that -
just 5 to 10 pixels).

--
Ticket URL: <https://trac.osgeo.org/geonetwork/ticket/290&gt;
GeoNetwork opensource Developer website <http://trac.osgeo.org/geonetwork&gt;
GeoNetwork opensource is a standards based, Free and Open Source catalog application to manage spatially referenced resources through the web. It provides powerful metadata editing and search functions as well as an embedded interactive web map viewer. This website contains information related to the development of the software.