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

proposition for alternative property for InProgressDataDate column in MARCO-BOLO_Metadata_Dataset_Record_WP5 #28

Open
laurianvm opened this issue Jul 18, 2024 · 7 comments
Assignees

Comments

@laurianvm
Copy link
Contributor

MARCO-BOLO_Metadata_Dataset_Record_WP5

Duplicate keys are not allowed in json(-ld)
--> meaning that the schema.org equivalent property of 'additionalProperty' for the columns "InProgressDataDate" and "EVDescription" needs to change for one these columns;
--> propose to change 'additionalProperty' into 'datePublished' for "InProgressDataDate"

Is this okay?

@kmexter
Copy link
Contributor

kmexter commented Jul 18, 2024

fine by me - would need to change for all the WP spreadsheets, mind

@kmexter
Copy link
Contributor

kmexter commented Jul 18, 2024

except ... these googlesheets do not need to be transformed, laurian. only the URIs they refer to. At some point we may (again) ask for metadata to be added here that will need to be transformed, but for now, not.

@laurianvm
Copy link
Contributor Author

only the value in cell D8 of the 'Column descriptions' tab would have to be changed (no other values need changing) - and this would only be to be aligned with what is actually used in the triples (but not required for things to work/not break)

@kmexter
Copy link
Contributor

kmexter commented Aug 22, 2024

Are we OK here? In that, the "in progress date" is not something you need to read into your templates. Can I close this?

@kmexter kmexter assigned laurianvm and unassigned kmexter Aug 22, 2024
@laurianvm
Copy link
Contributor Author

laurianvm commented Jan 12, 2025

with #36 duplicate keys issue disappeared on its own

however, https://schema.org/additionalProperty is not expected to be used on Dataset,
hence proposition to use:

{%- if _.InProgressDataDate %}
"datePublished": "{{_.InProgressDataDate}}" ,
{%- endif %}

@kmexter , @pieterprovoost or @pbuttigieg could you indicate whether schema.org-model needs to be rigidly followed? and which predicate is preferred in this case?

@kmexter
Copy link
Contributor

kmexter commented Jan 13, 2025

yeh, this is for @pieterprovoost or @pbuttigieg - not my expertise. I suggest that you two P's go thru the list of properties - col D of https://docs.google.com/spreadsheets/d/1jH8Gp50y9w_SsoFELYTKV6ohPlkO3nqm/edit?gid=115560455#gid=115560455 for example - and double check them

@pbuttigieg
Copy link
Contributor

pbuttigieg commented Jan 13, 2025

however, https://schema.org/additionalProperty is not expected to be used on Dataset,

It does validate and ODIS does use it on other types (we so reason for limiting its range).

That being said, there may be a better way.

hence proposition to use:

{%- if _.InProgressDataDate %}
"datePublished": "{{_.InProgressDataDate}}" ,
{%- endif %}

@kmexter , @pieterprovoost or @pbuttigieg could you indicate whether schema.org-model needs to be rigidly followed? and which predicate is preferred in this case?

"For data that are still in progress; please fill in an approximate date (YYYY-MM) you expect them to be published"

This says to me that schema:creativeWorkStatus should be set to something like "Incomplete".

If the value of creativeWorkStatus uses a DefinedTerm type, one can add the expected date of release in a description (or other) property of DefinedTerm.

One could just use text and say something like "Incomplete. Expected release on ..." but this isn't great.

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

3 participants