invalid schema and metadataNamespace fields in OAI-PMH ListMetadataFormats response

[tdilauro]

The metadataFormat chunk for prefix dataverse_json looks like:

<metadataFormat>
   <metadataPrefix>dataverse_json</metadataPrefix>
   <schema>JSON schema pending</schema>
   <metadataNamespace>Custom Dataverse metadata in JSON format (Dataverse4 to Dataverse4 harvesting only)</metadataNamespace>
</metadataFormat>

The value for metadataNamespace should be a URI and the value for schema should be a URL, but any URI will validate. In the short term, it might be reasonable to make up values in the http://dataverse.org namespace, so that the responses comply with the OAI-PMH 2.0 schema.

[pdurbin]

Another place where I thought about using a namespace for Dataverse was in the context of SWORD. I ended up using new QName(UriRegistry.SWORD_STATE... instead to yield <dataverseHasBeenReleased xmlns="http://purl.org/net/sword/terms/state">true</dataverseHasBeenReleased> but at the time I was wondering if we should have a URL under purl or under dataverse.org, like @tdilauro suggests.

[pdurbin]

These days we're using URLs like https://dataverse.org/schema/citation/... in our experimental Semantic Metadata API.

See this pull request for examples:

• IQSS/8533 Update Internal Semantic Mappings #8592

[sekmiller]

@tdilauro we are reviewing old tickets related to Harvesting. I was hoping that you could answer the following questions to help us determine if this issue is still open and if so, how to go about fixing it. Thanks!

What steps does it take to reproduce the issue?


•	When does this issue occur?

•	Which page(s) does it occurs on?

•	What happens?

•	To whom does it occur (all users, curators, superusers)?

•	What did you expect to happen?


Which version of Dataverse are you using?

[sekmiller]

I've reached out to the author of the ticket for more information, but it's possible that this is not applicable to DV 5.x since there's a reference in the original post to "(Dataverse4 to Dataverse4 harvesting only)"

It's difficult to estimate the effort without additional information, as I have not been able to reproduce the error state.

dataverse_json
JSON schema pending
Custom Dataverse metadata in JSON format (Dataverse4 to Dataverse4 harvesting only)

[poikilotherm]

Sorry to chime in, stumbled over this one.

Looking at https://demo.dataverse.org/oai?verb=ListMetadataFormats, it looks like we still are sending out that information.

It should be a very simple fix, looking at

dataverse/src/main/java/edu/harvard/iq/dataverse/harvest/server/web/servlet/OAIServlet.java

Lines 168 to 174 in 8b9d7f5

	private Context addDataverseJsonMetadataFormat(Context context) {
	MetadataFormat metadataFormat = MetadataFormat.metadataFormat(DATAVERSE_EXTENDED_METADATA_FORMAT);
	metadataFormat.withNamespace(DATAVERSE_EXTENDED_METADATA_NAMESPACE);
	metadataFormat.withSchemaLocation(DATAVERSE_EXTENDED_METADATA_SCHEMA);
	context.withMetadataFormat(metadataFormat);
	return context;
	}

and

dataverse/src/main/java/edu/harvard/iq/dataverse/harvest/server/web/servlet/OAIServlet.java

Line 100 in 8b9d7f5

private static final String DATAVERSE_EXTENDED_METADATA_NAMESPACE = "Custom Dataverse metadata in JSON format (Dataverse4 to Dataverse4 harvesting only)";

.

[sekmiller]

Thanks, Oliver.

[mreekie]

sizing: This is part of the OAI servlet. This could be possibly just changing static strings. There are two strings.We should put it in the bundle. This will not be coding. We just need to decide how to change the string to make it more appropriate.
This seems trivial so sized low

[mreekie]

Daily

• Originally we thought this would be just adding a URL to the metadata namespace.
• We don't have the same setup for the JSON schema however.
• We will need to make a sample, add it to the environment, and add the URL here.
• This impacts the size of this, possibly significantly.
• original size: 10

[pdurbin]

From talk after at standup, this this what we agreed on. Note that these are not real URLs!

This is from the OAI_ORE export. At the bottom, the dvcore value is https://dataverse.org/schema/core# . We looked at this example (dvcore is at the bottom): https://dataverse.harvard.edu/api/datasets/export?exporter=OAI_ORE&persistentId=doi%3A10.7910/DVN/TJCLKP

There's a lot more work to do to actually define the JSON Schema for Dataverse:

• bklog: Deliverable - As a system integrator, I would appreciate a JSON Schema for validating my dataset JSON before uploading via API dataverse-pm#26

All we're doing is adding two URLs so that https://demo.dataverse.org/oai?verb=ListMetadataFormats for example validates.

<schema>https://dataverse.org/schema/core.xsd</schema>
<metadataNamespace>
https://dataverse.org/schema/core
</metadataNamespace>