Hi List,
I’ve been looking at changing the formatter that’s used for the read-only “full” view for records to the angular one instead. However, I see a difference in behaviour between the view I get from testing the formatter and the view you get when it’s actually implemented in a record, and I’m not sure whether it’s a bug or an implementation problem.
I have changed the formatter setting in the admin console/user interface settings from:
/formatters/xsl-view?root=div&view=advanced
to:
/formatters/full_view?
This does show the angular view of the record, as expected, but the dropdown “more information” tab does not expand to show the other elements, and when I inspect the page in web console the other elements appear greyed out and no event seems to be triggered when I click the dropdown. I have experimented with root=div, and schema=iso19139, but they don’t seem to change anything.
However when I view the record using the same formatter in admin console/metadata and standards/formatters, the dropdown is activated.
I have seen that I can add a tab parameter to the formatters/full_view? URL and when I add (for example) tab=.gmd_dataQualityInfo then the correct tab is displayed but the dropdown remains disabled.
For information, the reason for this is to correctly show report titles (such as data quality/conformance reports) in the full view as they don’t seem to show using the standard settings. If it’s easier for me to change the standard full view then I am happy to do that, but I haven’t been able to figure out where to make the changes.
Thanks for any advice that anyone can give!
Jo
···
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009