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

b/2531 fix license resolution service url and missing extent/theme #11

Merged
merged 3 commits into from
Nov 5, 2021

Conversation

drspacemanphd
Copy link
Contributor

2531 - Fixes licensing resolution, and adds the correct geoservice url and spatial/theme properties

@drspacemanphd drspacemanphd requested a review from rgwozdz November 5, 2021 14:25
@drspacemanphd drspacemanphd self-assigned this Nov 5, 2021
Copy link
Collaborator

@sonofflynn89 sonofflynn89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple comments I'd like resolved before we merge, but thank you for taking this on!

@@ -342,7 +342,7 @@ describe('formatDcatDataset', () => {
const expected = {
'@type': 'dcat:Dataset',
identifier: `${siteUrl}/datasets/00000000000000000000000000000000_0`,
license: null,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@drspacemanphd I changed license to be null instead of '' for an issue a couple months ago. Are we sure we want to go back?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After reviewing, the switch to null was a style preference on Tate's part, not a product requirement. I'm fine to leave this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sonofflynn89 @drspacemanphd

It's not really a style thing on my part. It all comes down to the DCAT harvesters. Thomas told me that they seemed to prefer null, so I tried to be consistent with that. If it doesn't matter, this is fine with me!

Another thing to be aware of is that when you have a JSON-LD node, sometimes the entire node should be removed when one of the values isn't available.

E.g.

"foo": {
  "@id": "dct:somekey",
  "importantValue": null
}

I think adlib can do this by means of the "Optional Transform.".

@@ -12,5 +12,6 @@ export const baseDatasetTemplate = {
fn: '{{owner}}',
hasEmail: '{{orgContactEmail:optional}}'
},
accessLevel: 'public'
accessLevel: 'public',
spatial: '{{extent}}'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about the theme property mentioned in the issue?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently this comes along with extent

Copy link
Collaborator

@sonofflynn89 sonofflynn89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work!

@drspacemanphd drspacemanphd merged commit 3b11a61 into main Nov 5, 2021
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

Successfully merging this pull request may close these issues.

3 participants