Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research Task - ArcPro template for updating the definition associated with each field #813

Closed
tiffanychu90 opened this issue Jul 21, 2023 · 3 comments · Fixed by #860
Closed
Assignees
Labels
open-data Work related to publishing, ingesting open data research task Sub-issues within research request epics

Comments

@tiffanychu90
Copy link
Member

tiffanychu90 commented Jul 21, 2023

Research Task

Use this template to create issues that represent small chunks of work (.5 - 2 days) that stand alone, or represent incremental work as part of an Epic Issue Template.

  • Relevant PR (if applicable):

  • Question or Goal: We always submit DDP6/DDP8 excel spreadsheets for new open data layers to be published. One is the metadata XML for the entire layer, the other is the data dictionary. During the Geoportal inventory, the GIS team has asked for the data dictionary portion to be supplied in the automatic update, and not only in the email request. Previously, it's been ok to use a placeholder url because the spreadsheet gets uploaded manually on their end.

  • Research Required: Figure out how to work this into our templating process.
    The field name overwrite occurs with arcpy, and the definitions likely will be populated in that step.
    Need a robust enough process to accommodate the fact that we often add new columns, and they will need definitions.

The field info don't appear in the XML template -- double check this to be true.

Epic: #544
Related to: #802, #810

@tiffanychu90 tiffanychu90 added research task Sub-issues within research request epics open-data Work related to publishing, ingesting open data labels Jul 21, 2023
@tiffanychu90 tiffanychu90 self-assigned this Jul 21, 2023
@tiffanychu90
Copy link
Member Author

tiffanychu90 commented Aug 9, 2023

ArcPy docs...everything related to working with fields:

Nothing in docs indicates ability to change field definition beyond doing it manually. Changing it manually and exporting metadata....fields do not appear in XML, so we can't populate it ourselves.

@tiffanychu90
Copy link
Member Author

tiffanychu90 commented Aug 29, 2023

TODO

This was referenced Aug 29, 2023
@tiffanychu90 tiffanychu90 linked a pull request Aug 31, 2023 that will close this issue
@tiffanychu90
Copy link
Member Author

tiffanychu90 commented Sep 7, 2023

Temporary resolution

  • Move to metadata.yml and data_dictionary.yml as a simpler way for us to document what we want to input as metadata
  • Create for each dataset an FGDC template of fields. Then go in a update it update_data_dict.py and update_fields_fgdc.py
  • Apply the ISO 19139 template for each dataset and programmatically update that each month
  • Sync that in ESRI
  • Sync the FGDC template to bring in those field definitions/definition sources
  • Sync that to enterprise gdb

Temporary because FGDC apparently is being phased out and we won't be able to make use of this loophole as a workaround. We can take advantage of the fact that FGDC metadata can have ArcGIS metadata added to it, but not vice versa.
https://pro.arcgis.com/en/pro-app/latest/help/metadata/upgrade-metadata-to-the-arcgis-format.htm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-data Work related to publishing, ingesting open data research task Sub-issues within research request epics
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant