search

DOI-USGS / fort-pymdwizard

The MetadataWizard is a useful tool designed to facilitate FGDC metadata creation for spatial and non-spatial data sets. It is a cross-platform desktop application built using an open-source Python architecture.
https://usgs.github.io/fort-pymdwizard/
Other
63 stars 22 forks source link

Handle NoData in EA section #92

Closed ColinTalbert closed 6 years ago

ColinTalbert commented 6 years ago

Experimenting with ways to legitimately handle NoData values in a column.

This would get displayed like this: image

and get written out like this: image

dignizio-usgs commented 6 years ago

This seems like a decent option. Have you discussed the possibility of adding another field value that might not appear in the table currently being read? I'm not sure how many users have a need for this, or if it would complicate things but that was something else I was considering. The use case is admittedly probably small (someone using the tool to build a general XML, and interested in creating a stubbed out definition that might appear in other tables that use that XML as a template, etc.), but the 'Add a NoData' option you're showing there could also be a work-around for a user in trying to add another field value.

dignizio-usgs commented 6 years ago

The 'Definition' field (where a user can provide the explanation of what the value represents) could be slightly larger in the UI too.

ColinTalbert commented 6 years ago

There already is an option to add a new attribute, delete existing attributes, or add/remove domain values. Just right click and select from the dropdown.

Colin Talbert Data Manager, Analyst and Developer US Geological Survey, Fort Collins Science Center 2150 Centre Ave. Bldg. C Fort Collins, CO 80526 (970) 226-9425 http://orcid.org/0000-0002-9505-1876

Work schedule: Monday, Thursday - 7:00 - 5:00 Tuesday - Wednesday - 7:00 - 3:10 Friday (Telework) - 7:00 - 5:00

On Mon, Mar 26, 2018 at 12:10 PM, dignizio-usgs notifications@github.com wrote:

This seems like a decent option. Have you discussed the possibility of adding another field value that might not appear in the table currently being read? I'm not sure if users had a need for this, or if would complicate things but that was something else I was considering. The use case is admittedly probably small (someone using the tool to build a general XML, and interested in creating a stubbed out defition that might appear in other tables that use that XML as a template, etc.), but the 'Add a NoData' option you're showing there could also be a work-around for a user in trying to add another field value.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/usgs/fort-pymdwizard/issues/92#issuecomment-376259784, or mute the thread https://github.com/notifications/unsubscribe-auth/AWHgal07UJQFnSJQ3LvLYcnLOJ7b6RfWks5tiS78gaJpZM4S7oXx .

ColinTalbert commented 6 years ago

Agreed. I was trying to balance this against taking up too much real estate. Maybe if it auto expanded like a enumerated value.

Also decided against displaying the definition source for this domain value. I'd just use the one from above.

Colin Talbert Data Manager, Analyst and Developer US Geological Survey, Fort Collins Science Center 2150 Centre Ave. Bldg. C Fort Collins, CO 80526 (970) 226-9425 http://orcid.org/0000-0002-9505-1876

Work schedule: Monday, Thursday - 7:00 - 5:00 Tuesday - Wednesday - 7:00 - 3:10 Friday (Telework) - 7:00 - 5:00

On Mon, Mar 26, 2018 at 12:13 PM, dignizio-usgs notifications@github.com wrote:

The 'Definition' field (where a user can provide the explanation of what the value represents) could be slightly larger in the UI too.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/usgs/fort-pymdwizard/issues/92#issuecomment-376260855, or mute the thread https://github.com/notifications/unsubscribe-auth/AWHgapfWoBFfgZjUufNpNmJ1aaOmtzcnks5tiS_EgaJpZM4S7oXx .

afreeman-usgs commented 6 years ago

I think this looks good. I think we may need to treat it as a repeating element though, with 'add NoData' and 'Remove Last' buttons included?

ColinTalbert commented 6 years ago

How common are multiple nodata values in a column? I was hoping to avoid the complexity and real estate of having this as a repeating element.

I still think there's a balance between full compliance / having everything that anyone might need, and new users being overwhelmed by items needed for edge cases. This one could go either way.

afreeman-usgs commented 6 years ago

Yea, good point. I think it's rare enough that we could go with what you have already. I've only seen that a couple of times.