Update the packageId attribute in EML documents on update. Never display the local docid in the rendered EML.
Move the dataset metadata label for metacatui EML
Mark the entity metadata sections in metacatui EML transformations
Add classes and attributes to the object name and online distribution link elements in the MetacatUI theme.
Display text nodes in EML when the value is directly in the text node or in a <section> tag or in a <para> tag (in metacatui skin)
include type="party" attribute for the divs that contain contact information (for annotating with ORCIDs)
In the EML XSLT - Add classes to the entity details containers so they can be identified easily
include resource="#xpointer(...)" attributes for sections that are potential targets for annotation. So far we have the various people (creator, contact, etc) and data table attributes. https://github.com/DataONEorg/sem-prov-design/issues/18
download arrow on right side
remove "Package" from the default button, only use it when we have an ORE map id.
give the div that holds the download package button an id attribute so that we can dynamically change the content in there if/when we know the ORE map id instead of the EML id. https://projects.ecoinformatics.org/ecoinfo/issues/5948
do not use #none for the accordian control in method section
when 'printall' we should show the attribute coverage and method information, not a link to it
when 'printall' we should show the enumeratedDomain of a measurement.
use 'printall' option for the EML display - metacatui will scroll and navigate through all the metadata and has tabified the entity/attribute info. https://projects.ecoinformatics.org/ecoinfo/issues/5948
use glyph download icon, not a /knb/style/images path to an image (ugh!)
handle <references> element in <creator> for the citation.
use #view/{pid} pattern for the citation link, and then /object/{pid} for the XML download -- so no old Metacat API calls show in the rendered EML.
include $pid parameter and views/package endpoints instead of metacat API urls. Note that some links still exist for rendering portions of the EML (additionalMetadata and attribute details).
use <p> for thesaurus above the table of keywords
use "controls" class on Web Address
render keywords + thesaurus in a table structure
use <strong> for title rendering.
remove more ":" after labels
remove all table/tr/ cruft that is not used in main layout.
reformat attribute enumerated domain.
use "UTF-8" instead of encoding="iso-8859-1"
use "controls" class for common name element value
do not use ":" after labels.
remove all table/tr/td use
clean up detail tables for measurement type/scale/codes sections
render attributeList with side-bar navigation tabs for each attribute.
group the physical and distribution details together.
save point before tackling attribute list and other re-org in entity view
reformat physical/distribution/format sections of the entity display. https://projects.ecoinformatics.org/ecoinfo/issues/6037
reformat access control section (even though this will be replaced with SystemMetadata information). https://projects.ecoinformatics.org/ecoinfo/issues/6037
reformat usage rights
remove all tr/td elements in favor of divs
save point with Methods/protocol restyling - still some nested rendering to handle, but mostly accordianized. https://projects.ecoinformatics.org/ecoinfo/issues/6037
style all coverage fields w/o tables. https://projects.ecoinformatics.org/ecoinfo/issues/6037
comment out the general coverage/context header (will be anchor eventually)
eliminate all table, tr, and td tags in favor of <div>s or <label>s
style all other people entries. https://projects.ecoinformatics.org/ecoinfo/issues/6037
style Creators. https://projects.ecoinformatics.org/ecoinfo/issues/6037
save point: use "fake" input areas (wells) for the value in name/value pairs.
save point: reformat the General section
style citation in a "well". https://projects.ecoinformatics.org/ecoinfo/issues/6037
starting point for new KNB EML stylesheets (no tables--fluid divs...). copied the existing EML XSLs, will go from there. https://projects.ecoinformatics.org/ecoinfo/issues/6037