Dataverse: Geospatial Metadata fields not properly indented compared to other fields

Created on 20 Mar 2020  路  3Comments  路  Source: IQSS/dataverse

Version: 4.19

Hello everybody,

There is a discrepancy in indentation between the fields of Geospatial Metadata and those of Citation Metadata and Social Sciences and Humanities Metadata, as you can see here:

geogindent

The issue occurred in Firefox, Chrome and Opera.

Small

Most helpful comment

@BPeuch good catch, and thank you for reporting the issue. It appears that the recent layount changes to the metadata on the dataset pg in 4.18 (#6109) missed this label column width inconsistency. With a few minor adjustments to the stylesheet properties, we now have a consistent label column width of 25% because we have a consistent table width of 100%. The varying label column widths was due to varying width of the table. Now that the table is 100% of the panel width, that 25% label column width will hold consistently across all the blocks.

Screen Shot 2020-05-13 at 11 15 02 AM

All 3 comments

Version: 4.20

Hello everybody,

It looks like the identation problem now also occurs with the Social Sciences and Humanities Metadata box now that we've moved to version 4.20:

probindent

I believe there are now three indentation tabs, one for each metadata box. Maybe this will help detect the origin of the problem?

The issue occurred with Firefox, Chrome and Opera.

@BPeuch good catch, and thank you for reporting the issue. It appears that the recent layount changes to the metadata on the dataset pg in 4.18 (#6109) missed this label column width inconsistency. With a few minor adjustments to the stylesheet properties, we now have a consistent label column width of 25% because we have a consistent table width of 100%. The varying label column widths was due to varying width of the table. Now that the table is 100% of the panel width, that 25% label column width will hold consistently across all the blocks.

Screen Shot 2020-05-13 at 11 15 02 AM

Wonderful! Thanks a lot for your feedback, @mheppler, and to everyone else for tackling this issue so quickly.

Was this page helpful?
0 / 5 - 0 ratings