terraframe / geoprism-registry

GeoPrism Registry is a system for curating interlinked data through time. It's the first framework implementing the Common Geo-Registry specification.
https://geoprismregistry.com/
GNU Lesser General Public License v3.0
18 stars 5 forks source link

Possibility to edit the label, description and options for the default fields attached to a GeoObject type (unique ID, status, coordinates,...) #146

Open SteeveEbener opened 4 years ago

SteeveEbener commented 4 years ago

The label and description of the fields containing the unique identifiers and names (English and default) should be editable and these labels being used as the header of the fields in both the master lists and the exported spreadsheet (column headers and data catalog) remembering that software like ArcGIS do not handle well headers that are longer than 10 characters

SteeveEbener commented 4 years ago

The fields containing the latitude and longitude for point type objects are also not appearing in the list of attributes while they are being generated by default (they are appearing when you create a master list)

SteeveEbener commented 3 years ago

The status field is to be added to the list of the fields mentioned in the previous posts here. In this case, there would even be a need to be able to modify the "code" attached to each label and potentially to add more labels as well

rfromthecastle commented 2 years ago

Enhancement raised by Yongjoon Park (WHO Laos) on 24/06/2022. Specifically "Geo-Object Name" would be better changed to the attribute name listed in the data dictionary.

rfromthecastle commented 1 year ago

Raised again by Xongyang and @viengthong2015 from the Laos Health Information Division IT team on 11/01/2023. In Laos, DHIS2 organization units have a variety of codes (i.e., DHIS2 UID, DHIS2 Code, HFID, etc.) and to reduce confusion, it would be helpful to be able to edit the names of default attributes such as the Code or Display Label.

rfromthecastle commented 1 year ago

Hi @justinlewis, saw your proposed solution to edit these through the localization spreadsheet. Can these default attributes be renamed in the spreadsheet per Geo-Object Type or does e.g. a rename of 'Code' apply to all Geo-Object Types?

rfromthecastle commented 1 year ago

@justinlewis and Nate to test that default attributes can be updated for each Geo-Object Type via the localization spreadsheet.

rfromthecastle commented 9 months ago

Confirmed that this is editable through the localization spreadsheet

SteeveEbener commented 9 months ago

@rfromthecastle : is it now confirmed that the localization of these attribute can be done object type by object type through the localisation spreadsheet?

rfromthecastle commented 9 months ago

@SteeveEbener Yes, confirmed. We were able to change the Geo-Object 'Code' attribute to 'HFID' for health facilities only in the Laos instance using this method.

SteeveEbener commented 8 months ago

Thanks @rfromthecastle. Did you have to create a completely new localization file or could you modify the default English one?

rfromthecastle commented 8 months ago

Hi @SteeveEbener, we modified the localization file you can directly export from the Settings module, and were able to do this for both English and Lao.

SteeveEbener commented 2 months ago

@rfromthecastle : Can you please provide the key for the label in question (unique identifier, name, geographic coordinates)? Thanks

rfromthecastle commented 2 months ago

Hi @SteeveEbener, what do you mean by 'key for the label'?

SteeveEbener commented 2 months ago

This image

rfromthecastle commented 2 months ago

Hi @SteeveEbener, looks like changing attribute display names for lists is done at the list version level rather than set per Geo-Object Type. The screenshot below (Registry Metadata tab in the localization file) shows the keys where the defaultLocale values are defined for each attribute, but only for one list version. Any newly generated versions would still display, e.g., 'GeoObjectType Code' as the code instead of 'HFID', and would need to have the defaultLocale values be manually updated and reimported, which would be a tedious task.

image

As such, this ticket would need revisiting @justinlewis

SteeveEbener commented 2 months ago

@rfromthecastle : Thanks for identifying this. Much appreciated