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

Geo Aardvark: schema changes #1514

Closed
3 tasks done
marlo-longley opened this issue Aug 29, 2024 · 1 comment · Fixed by #1516, #1515 or #1517
Closed
3 tasks done

Geo Aardvark: schema changes #1514

marlo-longley opened this issue Aug 29, 2024 · 1 comment · Fixed by #1516, #1515 or #1517
Assignees

Comments

@marlo-longley
Copy link
Contributor

marlo-longley commented Aug 29, 2024

  • Only georeferenced maps should have the class 'Maps.' Currently, all raster data are classified as Maps (ex. Bathymetric GeoTIFFs such as this one: https://earthworks-stage.stanford.edu/catalog/stanford-wc605vp7672)
    The mapping logic for gbl_resourceClass_sm should be the same as it is for the gbl_georeferenced_b element:
    IF title.value CONTAINS '(Raster Image)' > Resource Class = Maps

  • For dc_source_sm element: Only create this element if the item has a PURL. Apologies for not catching this sooner, but there are some georeferenced maps that have been sourced from other applications (such as the David Rumsey Map Collection site) and the identifiers that are generated will be invalid, see the dc_source_sm element this example:https://earthworks-stage.stanford.edu/catalog/stanford-yx324nv8969/raw

  • Update dcat_theme_sm mapping (see below)

@thatbudakguy thatbudakguy changed the title Geo Aardvark: schmea changes Geo Aardvark: schema changes Aug 29, 2024
@thatbudakguy thatbudakguy self-assigned this Aug 29, 2024
thatbudakguy added a commit that referenced this issue Aug 29, 2024
Part of #1514

This changes the indexing strategy for resource class to use a
MatchMap to make it much simpler to get map/dataset values out
of the data.

It also ensures that any georeferenced images are counted as both
maps and datasets.
thatbudakguy added a commit that referenced this issue Aug 29, 2024
Part of #1514

This changes the indexing strategy for resource class to use a
MatchMap to make it much simpler to get map/dataset values out
of the data.

It also ensures that any georeferenced images are counted as both
maps and datasets.
@kimdurante
Copy link

Hi Again. I cannot edit this ticket, so I'm adding this here in the comments.
Because the Aardvark schema uses modified terms for some ISO topic category values, I would recommend the following for mapping for the dcat_theme_sm element:

IF subject*.source.code = ISO19115TopicCategory AND subject*.value = Climatology, Meteorology and Atmosphere > Climate

IF subject*.source.code = ISO19115TopicCategory AND subject*.value = Planning and Cadastral > Property

IF subject.type=topic AND subject.value = Aerial photographs OR Aerial surveys OR Bathymetric maps OR California as an island--Maps OR Composite map OR Landsat satellites OR Multibeam mapping OR Nautical charts OR Remote sensing OR Remote sensing images OR Satellite image maps > Imagery

IF subject.type = topic AND subject.value = Coasts OR Forests OR Forest canopies OR Forests and forestry OR Hydrology OR Hydrography OR Land cover OR Landforms OR Vegetation mapping > Land cover

OTHERWISE IF subject*.source.code=ISO19115TopicCategory > subject*.value

I hope this is not too confusing, happy to chat about it. This one is not a huge priority for me due to the fact that subjects and themes are inconsistently applied, and also that metadata for scanned maps do not include ISO topics, so a complete mapping to the dcat_theme element will require much more analysis, especially as we add more maps to EarthWorks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment