Well, welcome to this webinar, and I'm really happy to see that there is so much interest. Just noticed that there were over 100 participants, so that is really exciting. Sophie and I will give you an update on what has changed in the schema version and how you can benefit from it.

My name is Madelene Desmale, I work at the TU Delft library in the Netherlands, and I'm co-chair of the metadata working group. Sophie, do you want to say something to introduce yourself? Good morning, everyone. I'm a member of the working group, and I work as a librarian at the

National Research Council of Canada. Thank you. Here is a short overview of what to expect in this hour. Please note that there will be a live Q&A session, so submit any questions you may have

in the chat or save it for later. And if time permits, we will also have a feedback session on the work of the metadata working group, we will use Mentimeter for that. So keep your mobile phone and or another device ready.

The metadata working group consists of the following members, a nice mix of people with both a technical programming background and librarians. The metadata schema is the backbone and at the heart of data side services and has

become a widely known standard. The metadata working group maintains data sites metadata schema in consultation with data site members and under the guidance of the data site board.

A short tech update to start with, to support the new metadata schema, data site is updating the services to enable users to create and update the UIs with the new metadata schema. The changes to the data site services to support metadata schema 4.4 are carried out

in two phases to enable immediate access to non-breaking changes. Phase one, which was released at the end of March, includes support for metadata schema 4.4 that does not require breaking or complicated changes to the

REST API version two. Please note that related item, which is one of the new changes to the schema version, is currently only available via the MDS API and XML file uploads in the

Fabrica interface, so not via the form. Phase two, which will be released later this year, will include support for the REST API version three and Fabrica, and via via the Fabrica interface.

Version 4.4 is backwards compatible, meaning that the changes made don't affect preceding minor releases of version four and of version 4.0.

You only need to specify the major version in your metadata submission, so you can already take advantage of these updates without having to change anything else about how you send metadata to data sites.

Please note that version three of the metadata schema is still supported, but be aware that version three is the preferred one. Focus of 4.4 is to provide better support for textual publications, and although it

has always been possible to register DOIs for text publications, there was a great need from the user community for metadata fields in which information related to text publications could be included in a structured way.

And since we are not solely focusing on research data, we have decided to reflect that in the title of the documentation. So you may have noticed that the title, you have added other research outputs at the end of the title.

Just a few numbers that show that more support for text publication is warranted. The number of registered DOIs for text publications with resource type text is almost the same as for data sets. After data sets, most DOIs are registered for text publications, so it was about time we started to pay more attention to this.

And now we really get to the schema updates. The first change I want to highlight is related to the subject property.

Subject terms describe what the research is about, usually derived from some type of vocabulary or schema. Applying structured term entries provides greater consistency in search results for users.

Subjects also group related resources and enable exploratory browsing and searching. And that's why this property is in the schema documentation indicated with the gray shades, meaning that it's a recommended property. And in addition to the sub-properties, subject scheme, scheme URI, and value URI, the new sub-property classification code has been added

to indicate the classification code associated with the subject term in a subject scheme. To give you a little bit more detail, an explanation of what we mean by this.

The most widely used subject classification we currently find in data site metadata is the Australian and New Zealand standard research classification fields of research.

The subject scheme is broken down into divisions, the broadest level with two digits. In this example, it's chemical sciences. Then you have a category of finer detail, which are the groups with four digits, and

then the fields, the finest level with six digits. And these six digits indicate the classification code related to the subject term. This is an example how that looks like. In this example, the classification code is particularly useful

because the subject scheme, that is Australian New Zealand classification scheme, does not have value URIs for each subject term.

Instead, the classification code can be used, can be added that identifies the subject term related to that classification code. But of course, when the subject scheme is supporting both value URIs and classification codes for subject terms, you can use both sub-properties.

Another important change is the addition of specific resource types, such as journal, journal article, dissertation,

etc. And also includes computational notebook and peer review, so that these types can be better identified. We believe this is a huge improvement compared to previous schema versions, where you can only select text with optionally the resource type property to indicate more detail.

The only exception between all these text related resource types is computational notebook. Computational notebooks are virtual notebook environments for used for programming and computing and a well known example is the Jupyter notebook.

And because we've seen enormous growth in the use of these platforms, we felt that we should support that. A special note about output management plan.

Data side supports data management plan identifiers, since the schema version 4.4. A DMP ID is a unique persistent identifier for a data management plan. A DMP ID is a DOI with a resource type general output management plan.

And since the release of this schema version, this resource type general is now included in the schema. And with the term output management plan, we cover both data management plan and software management plan. And

I think I will now hand over to Sophie, who will explain more about the related item property.

Hi everyone. And I The next. Madeline. Yeah, I think I need to stop now and stop sharing or Okay, yeah, I will share my screen move to the next slide.

This is the other change in schema 4.4 that we wanted to share with you. It's the addition of a new relation type value is published in The relation type is a sub property of the existing related identifier property 12 and the new

related item property which we will present in the next few slides with this new relation type. The relation type value is published in you're able to refer to the container or series in which the described object is published.

We consider the series or other containers like journal book to be a related item. The last change we present is the addition of a new property related item. It was added to accommodate at least two use cases first to provide structured text citation information.

The initial requests for structured text citation that and this was the main driver for this change have come from data site clients who do have an identifier for related items, but who's aggregators have additionally asked for explicit text citations, the new related item property accommodates that initial requests.

It also accommodates a second use case to provide information about a related item that does not have an identifier. You can now include a related item with or without an identifier and you can include parsable metadata about each related item.

So, as I just mentioned related item can now be used to include citation publication information or series

information of related resources with or without identifiers sub properties included were chosen to facilitate both use cases. All sub properties are optional except for two which express the type of relationship related item is used both.

Sorry, two of the sub properties. are mandatory and they express the type of relationships when related item is used both the related item type and the relation type are required.

Be aware that for related item type, the same control values can be used as for resource type in property 10. And that for relation type, the same control values can be used as in sub property 12b. This example.

shows Okay, it shows how series information like series title volume issue page numbers can be included in a discrete specific designated sub properties in this example, the described resource is the journal article.

Which is published in a journal. The related item includes information about the journal title volume, etc. In the previous schema versions series information could be included as part of the description property with a description type series information.

And, but it was just an unstructured unstructured text string of which the various elements are difficult

to parse so all those series information is not deprecated we strongly recommend using the new related item property, this example shows how related item can be used to provide metadata about a report series.

In this example, the described resources, a report. That is published in a series with a series number another example here the described resource is a book chapter.

Which is published in a book, the sub properties include the publication information related to the book, and it includes editor, which is indicated in the contributor.

sub property here's another example, this one is of a paper published in a series, but it is a reprint of an article that was first published in a journal.

So the related item describes the original journal article. And the related item, then can provide the DOI of the journal article the title of the journal article and its publication, we have one last example for related item.

This one, it shows how a citation information number resource related to the one being described can can be included in the metadata in this example, there is no related item identifier.

But it includes important citation information creator title publication year and publisher, I will stop sharing and. back to Madeline.

slideshow sorry about that.

Yes. yeah what to expect next well first. I would like to update you that we will make available soon the updated crosswalk between data site and Dublin

core but just about to release that and it will be announced separately, I think, in a few weeks now. When it's available. And after that we will start our work on the next version, and we have already some topics on our working list, of course, suggested by the Community.

And this is just a few examples, but of course our list is much larger. And. If you have any.

suggestions yourself. And be it a minor or major change value would normally welcome your suggestions and the schema is ultimately there for you and should meet your needs as much as possible, so questions and any comments about the schema are would be highly appreciated.

You can use the feedback link. At the. Of the Google discussion group on the schema homepage at schema.data site.org or just send a note. To support at data site.org it's not yet decided if the next version will be a major release

or another minor release just depending on the topics how big they are and if they affect any changes. To the of the break the changes to the to the preceding minor versions of schema.

For okay, this is this are the updates about the schema and there is now time to take. Questions from you.

So we don't have any questions in the chat. The moment does anybody have a question for Madeleine or Sophie at this point, yes, as Susan is it possible to capture citations from within an article.

From within an article. Can you give me a little bit more.

Context about it. I think it can we do have sub properties that are related to. To general information is that what is meant.

From the reference lists at the end of an article. Oh, at the end okay citation yes about in principle it's it's you should be able to include that in the related item property, because we support related items support title of course authors.

publication here, yes, you should be able to include that information in related item property. Yes, and our last example for the related item we showed a relation type is cited by. yeah so that can be used for references or sites is the other than I

think in the this particular question sites would be the relation type that would be most. Appropriate yeah. Okay, great thanks Susan, then we have a question from holder saying how is the upcoming support for kids for instruments going to look like.

And we have to figure that out, yet we will it's I think it's an suggestion that came up in an RDA working

group, so I think we will align with that group on that so but it's not figured out how that will look like. We just have to start with discussions about that is that an answer on your on the question i'm not sure.

it's maybe a bit bit fake yes that's yeah this is. yep that sounds good, I think, so, then we have another question from a delay saying is the updated schema already in use.

Yes, it is in use, yes it's published on the data side of schema homepage schema dots data side.org you can find it there yeah. I will share the link to that. Okay, and I think that's all of the questions that amy has a question here, could you say again

whether it was the form of the file upload for fabrica that has been updated to support the new schema. Yes, the for the form is. almost. supporting the full schema, except for the related item.

property, but I suppose we will share the slides after this session. Yes, so the file upload supports the full XML. yeah exactly yeah XML is supporting the yeah yeah the full schema yeah.

Okay, another question here is. About relation type is version of seems to go only one way from version A to version B. But how would you describe the relation between. Two publications that are more or less the same, but only the title page changes, we see

that in some publications, where the same book is published at two different publishers weird but true. And would you recommend is variant form of. i'm not I don't know out of my all the relation types but.

You, would you repeat the question because I form is for. A different format. Well, the question is about relation type between two books that are. Very similar, but very similar, but not the same, and so you have a the relation type is version of or

you have is variant form of, and so I think they're just asking for some clarification about the difference there but right. As version is version of.

An instant of a target resource is version of indicates a is a version of B, whereas is new version

of, as you said, goes in a specific direction and is previous version of goes in the opposite direction yeah all three exist Okay, so you have a backwards version of backwards way of describing his version of his previous version of. Okay okay.

So the next question is when will the metadata schema form be modified according to the update or has this been done. So the work around the form and I think.

I don't know if Martin you're on the call if you wanted to speak about that briefly well this work is scheduled, I know this work is scheduled for quarter three. Of this year, so.

As you said Madeline it was already the is published in the new resource type is is already supported and. yeah all the source types are supported. Only the related item property is only available.

In the mds API and find the xml upload in fabrica. But in in the quarter three of this year, the full metadata schema will be supported in API rest API version three and in the fabrica interface yeah. Great okay so, then we have another question that says, could you repeat the timeline for the rest for the updated rest API and

when we can use 4.4 with the rest API so that's also quarter three I think when this will be supported in the form. Yes, I'm not I'm not I'm not sure about in real exact timeline and that's.

it's not my. My. area. yeah no worries, I think I think we can say Q3 for now, so let me just see it was quite a few questions coming in, so I just want to make sure. We have time for this, or you have another section.

yeah okay so. Okay question regarding versioning the documentation on versioning does not clarify when you would recommend versioning such as Crossref does. What exactly is a minor change versus a major change so slightly going off towards something different here but.

I don't know if you feel you would like to comment on that Madeline or Sophie. Well, a major change will be. Will be released when there are breaking change with preceding minor versions of the release of the version four.

Oh sorry, I think this is referring to when to assign a new DOI to a different version of. yeah yeah so. So in the schema documentation, there is it's up to each individual steward to decide to decide when a new

DOI should be assigned to a major new version of a resource, and so I think this question is about. What is a major change to a version of a resource that's being shared. Well, I will say if the content has changed and the data files or.

or important metadata has changed, then it's. recommended to issue a new DOI, but there is only a small typo somewhere in the metadata, then you can you don't need immediately to update with a new DOI.

But that is also more yeah. Okay. How I would explain it but yeah. yeah I think that's good. Feel free to keep adding more questions or more context, if you want more information in the chat so just one last question here, I think that says.

On the last slide support for PIDs for instruments, did you mean data collection instruments and instruments.

With instruments it meant the instruments by which data are collected, for example. That is what I how I would explain instruments. So, for example, you can add an identifier, for example, to measuring instruments or maybe a radar somewhere, and then you can.

attach a UI to that instrument and which allows you to collect all data sets. generated by that instrument, for example. Okay.

Great so finally let's just answer this question, is there a way to comply with the initiative for open citations other than connecting the single citations via the related item. um well, I have to apologize for that i'm not sure I would not see how to

answer that question, I will take that to the metadata working group if it's if you don't mind. yeah. yep good question okay, thank you.

All right. Okay, so, then we have a sort of comment here that says social sciences use instrument to refer to a, for example, questionnaire, which is different from a physical machine like a telescope or a microscope. Okay yeah.

So, then we have a final comment that says, could you please share the slide to about instruments again okay. That seems to be causing some. interest yeah.

yeah well it's a new topic yeah so it's something that we should start that we are now starting the discussion about in our working group so. But if there is so much interest and we can perhaps update you. Somewhere in between our.

Discussions i'm not sure yeah. Okay, great and I think and here's a question which resource type general do I use for an article in a collected edition book part is not possible, should we use book chapter.

An article in a book edition. In a collected edition. In collected edition. yeah yeah so we do you know, and you are more of the text publications, but I will say chapter but.

We have that challenge with mods also and we we choose to use chapter yeah. Okay, great Thank you, there is some more text. Happening, but I think I don't think we have.

Any specific questions so would you like to move on to the. yeah can can we save the questions in the chat Mary, do you know that. yeah I should be able to export them okay yeah Thank you okay. Yes, um I think we now come to the feedback session.

We would like to gather your feedback about the use of the documentation and does it does it work for you, are there any challenges and what you expect from us regarding communication, so if you prepared a few questions for that much so maybe Mary you can share, I will need to stop sharing, I suppose.

yeah yeah sorry okay. And if you would like to go to menti.com. and enter the code that is on the screen and the first question is just to get a sense.

How often you use the schema documentation yourself now it's interesting to see this numbers that are also people on the call who.

Rarely use the schema documentation would, of course, mean that they are not in a position to register the UIs or that they are used to register the UIs it's the same metadata and that there's no need.

To change that just let me know when you want to move on yeah Thank you, I think it's really interesting for us to know yeah you can move on to the second question okay great.

We would like to know if the documentation works for you and over the years, it has grown to a to a big monster that may be difficult to handle so we wondered. If it would help if the documentation very split split in, for example, resource type so that only

document information that applies to that specific resource is offered, and you can think of, for example, a schema. specifically for text publications or a schema specific for data or schema specific for software.

Would that work better for you, what were the different profiles you had in mind there you just said yeah just and then just another.

Separate schema just forget the word profile just a separate schema for a specific resource type. And we have now and really concise edition of it for everything, and if you're, for example, working only with text publications, would it be helpful if you have only a schema.

metadata schema only related to text publications I don't know if there's an issue here or.

Is the voting working it shows 41 responses oh yeah that's a shame. Okay, let me see if I can there we go oh yeah oh that's better.

Okay, so thanks yeah, I think we can move on to the next question

yeah this question is about communication, how can we improve communication to gather your feedback. Which channels to use whether they are specific training needs for a schema documentation, etc, and you can please enter any suggestion, you may have.

Well, thank you it's really useful feedback to know that more examples are needed, I

think the metadata working group was always a little maybe a little bit reluctant but. Too much examples but. If that works best, and I think we should do this. yeah still a few answers coming in.

yeah well thanks. And then, I think there is a last question yep it's quite it is a quite open question again. Do you have other suggestions for us that we should be working on think of improving in the schema documentation think of layout.

structure, the language or if we should work on interoperability with other schemas and which or any other topic. Please enter any suggestion, you may have yes, and I can already say that schema.org is on our list and has been asked.

Previously yeah good practice is shown as a big word, so I think that's it's also something that should have our attention.

Or at least attention of data side i'm not sure. Okay, well, thank you. yeah that's great yeah okay.

i'll stop sharing well, I think. The end well. it's very tough final slides and I just want to thank you for your joining this webinar for your

suggestions for your valuable feedback and well, if you want to to get in touch with us, please do. And we welcome any suggestion, you have, and I would like to thank Mary for your support preparing this webinar Thank you.

Thank you.