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

alternate relations then parentidentifier #230

Open
pvgenuchten opened this issue Aug 4, 2023 · 0 comments
Open

alternate relations then parentidentifier #230

pvgenuchten opened this issue Aug 4, 2023 · 0 comments

Comments

@pvgenuchten
Copy link
Contributor

pvgenuchten commented Aug 4, 2023

some of the iso and geopython tooling allows to model alternate linkage between records then parentidentifier, this is of interest when the linkage has a different nature.

in iso, this type of linkage is managed via the aggregation-info element. OWSlib is able to extract this info. pycsw captures this information in the record.relation field.

would be interesting to add this option to the pygeometa model, probably close to the parentidentifier element? aggregationinfo uses a code list to identify what type of relation is involved, it could be interesting to add that option (but OWSlib and pycsw currently don't capture this information).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant