Rachael Lammey: Okay, welcome everyone. I can see the participant, the participant number ticking up as people join this demos experiments. And Q&A session today.
Rachael Lammey: thank you for joining and hopefully, you will find lots of relevance interest and things to ask questions about over the over, the course of the session.
Rachael Lammey: it said, I'm just going to give a few more minutes in case anyone else is trying to join. Find the link. All of those kind of things, and then we'll get started.
Rachael Lammey: Okay, so let's let's go to the the next slide.
Rachael Lammey: So again, just
Rachael Lammey: for some of you who've joined the earlier sessions today. You'll have heard our notes. But just to make you aware of Cross Ref's code of conduct. If you are on
Rachael Lammey: if you are on mastodon or X, then you can join the discussion. We'd welcome you to do so on those platforms.
Rachael Lammey: But I think probably the most effective thing for this session is, if you've got questions, use the QA. Box to pose those to our our presenters. We're going to take questions for each of the presenters, after after each of their sections. So that they're still fresh in your mind, and we will share the slides and recordings.
Rachael Lammey: Afterwards. Next slide.
Rachael Lammey: I'm the
Rachael Lammey: reminder. You've got, I think, around 2 h left. So if you haven't voted for the 2023 board slate, then
Rachael Lammey: our ballots close pretty soon, but if you wish to submit a vote or change your proxy, vote, then then let Lucy know in her emails in this. So we've got a really good interesting slate of candidates this year. So part of being a member of Crossref is having the capacity to be able to vote and make sure that our Board is as representative as possible of you and your communities and your needs. So we'd really encourage you to do that
Rachael Lammey: next slide.
Rachael Lammey: So I'm going to start by introducing the session. As I said, this is product demos, experiments and questions for those who are willing to to present would say, the aim of this session is to give a view across the things that we are at the early stages of exploring and working on both from the product and development teams and also you'll see strong representation from the from the labs team across Ref as well.
Rachael Lammey: We're gonna give some hints and tips for using our Apis
Rachael Lammey: ones that you're probably very familiar with, or would like to get more familiar with and newer ones as well, and then external integrations with our with cross ref from our colleagues at the Public knowledge project
Rachael Lammey: for whom it's very early. So so thank you, Eric. Each demo will last for around 1520 min, and we should have time for questions for our panelists. So Luis and I are. Gonna keep an eye on the QA. And try to make sure that those get to the right people at at the right time.
Rachael Lammey: So
Rachael Lammey: our first demo is
Rachael Lammey: is currently under development. So again, we've got for a couple of these things are under active development. We've tried to step away for them and not from them, and not touch them for the for the purposes of the Demos today, but as any of you have done, a live demo know they can be all sorts of fun. So
Rachael Lammey: kudos to my my colleagues but our first demo is of our currently under development registration form for for journal content. Lena Stall will share a sneak peak of the work that we've been doing to create a simple user interface to make it easier for members to register good quality journal article metadata.
Rachael Lammey: So over to you, Lena.
Lena Stoll: Thanks very much, Rachel. We're actually starting out quite safe. I'm not doing a live demo. I just have screenshots and slides so everyone can relax for the next 1015 min, and then it gets really exciting when people start doing things live.
Lena Stoll: yeah. Great to be here today for the many of you who don't know me yet. As Rachel said, my name is Lena. I joined the product team at Cross-ref over the summer
Lena Stoll: I'm based in beautiful gray Berlin, Germany. And
Lena Stoll: I'd like to tell you a little bit today about the work that we've been doing to develop. As Reisha said, a simple user interface or ui to allow members to register journal articles. Without having to touch an Xml file.
Lena Stoll: I say, we have been doing this work, which is quite generous. For myself, because I've only been here a few months and actually on the product side, most of this is the result of a lot of work by my colleague, Sarah Berman, who many of you might know better. But I've taken on this work because, she recently went on, Maternity leave
Lena Stoll: so just in case you're wondering why there's a new face talking about this and on the tech side shout out to Patrick Vail. I know you're watching.
Lena Stoll: Okay? So anyway, what we're doing there is
Lena Stoll: basically an extension of the concept behind the new grants registration form that we released, I think, towards the end of last year, that some of you might have used before or seen Sarah Demo in the past. So a lot of this might be familiar. If you're
Lena Stoll: if you're familiar with that tool.
Lena Stoll: So if you go to the next slide, please.
Lena Stoll: yeah, I just want to acknowledge that
Lena Stoll: some people of the audience might be thinking.
Lena Stoll: aren't there already multiple ways of
Lena Stoll: registering records, especially journal articles? And it's
Lena Stoll: 10 points to you if you recognize all of these options I've represented on this slide, and if you can name them all
Lena Stoll: we have our trusty old web deposit form that you can see at the top. Right? We have a metadata manager. We have a plugin for Oj. S. For those that use that platform to manage their journal articles. We have an admin console where you can upload Xml files if you're able to create them. And then, of course, there's the option of depositing Xml in an automated way to our Apis.
Lena Stoll: using Https post, which is represented on the bottom right. and
Lena Stoll: that is, of course, the most kind of
Lena Stoll: reliable, scalable, efficient way of registering metadata. But we do know that
Lena Stoll: today the majority of our members are either institutions or their small publishers, and not everyone runs an Xml first workflow. Not everybody even has the
Lena Stoll: technical resources to or know how to create Xml automated way and deposit it. So we do want to offer.
Lena Stoll: These user interfaces that allow everyone to at least perform all of the most essential tasks that you need to do to be a good cross-ref, citizen.
Lena Stoll: but the goal isn't and can't really be to represent absolutely everything that you could do with direct calls to our Apis through a user interface. Because with, if you're familiar with our metadata schema, the sheer complexity behind everything that
Lena Stoll: you can in principle register with us, then you'll understand that that's not really realistic to do in a form that people still have a fighting chance of actually using.
Lena Stoll: But that's just an aside
Lena Stoll: getting off my virtual soapbox. I guess the main point of this slide is just to say
Lena Stoll: all of these different routes. All of these different roads ultimately lead to the same database and to the same Api's. So why
Lena Stoll: would we bother creating yet another tool for depositing?
Lena Stoll: And if you go to the next slide.
Lena Stoll: actually, each one of the tools that we've built so far that work around the requirement to work with a with Xml files directly, all of them serve their own little niche of use cases.
Lena Stoll: and you have to be pretty familiar with the cross-ref tool ecosystem to kind of understand which one is the right one to use, for which purpose and each of our tools also has its own kind of specific limitations.
Lena Stoll: For example, metadata manager is very complex technically, and for that reason it has a number of bugs and issues that we're aware of, that we've never been able to and fully address. The web deposit form is a little bit awkward to use, and it doesn't cover all record types, and so on, and so on.
Lena Stoll: And all of this together kind of leads to a confusing user experience for those members who are trying to deposit their metadata manually, and it's also quite inefficient for us to have to maintain all these different tools in parallel. They're all different code bases.
Lena Stoll: if we make a change to a metadata schema, for example, we have to then, as a result of that, make multiple changes in multiple places, to to reflect that in all of our tools, and so what we've been building
Lena Stoll: yeah, since. Since we started with the Grant's registration form last year. And now with this general article, registration form is
Lena Stoll: different, because it is being built in and what we call a schema driven way.
Lena Stoll: And by that I just mean that we're we're creating the interface, the form that you actually enter permitted into
Lena Stoll: in an indirect way from
Lena Stoll: the schema itself. So it takes the schema as an input and then creates a form out of it, which means that if there's a change to the schema, it's much, much easier and much faster for us to reflect that in the actual interface
Lena Stoll: and it's also an interesting both of concepts for the wider community to show that it is possible to build your own interfaces in that way that suit your specific needs.
Lena Stoll: Because, as I already said earlier, we will likely never be able to build the ultimate
Lena Stoll: one single tool that is usable that. But that also allows you to do absolutely everything that you could do if you were talking to the Xml Api directly.
Lena Stoll: And so the idea is that if we build a unified set of forms like the grants deposit form and like now the new Journal article form
Lena Stoll: eventually we'll be able to replace
Lena Stoll: some of the tool tools that we know aren't really
Lena Stoll: serving a community in the way that they could.
Lena Stoll: I'm talking specifically now about Metadata Manager, which. if you've used it lately, you've seen a little banner at the top. You'll know that we've been planning to deprecate that for a while now.
Lena Stoll: and if you want to read more about the reasoning behind that decision, and why we're doing what we're doing, then there's a blog post linked on this slide that Sarah wrote a little while ago, called Next Steps for content registration.
Lena Stoll: And we're also building all of our new tools in a way that they are easily, automatically translatable. That's a process called localization. And that they can also be used by users with disabilities.
Lena Stoll: Okay, so that's the preamble. If you go to the next slide. I just wanted to show you a few
Lena Stoll: screenshots. Hope they're not too small in your screens.
Lena Stoll: Just of the current state of the prototype of this film that we've been working on. It's still at a very early stage, as Rachel kind of gave it a little disclaimer at the beginning and a bit of a warning. But I just want to show you. Just give you a little bit of a flavor of what I'm talking about.
Lena Stoll: So if you've used the Grant's registration form in the past, or if you've seen it, then a lot of the kind of design of this interface is going to look quite familiar to you.
Lena Stoll: We're deliberately keeping it very simple. So
Lena Stoll: sorry these screens aren't particularly shiny or telephone but we're focusing on the
Lena Stoll: most important, the most widely used fields in the metadata schema for journal articles and
Lena Stoll: just again, not every little thing, but the schema in theory allows, for in an Xml file can be represented in a form without making it so complex that it doesn't work for any anyone anymore. But we're focusing on the most important field just to make sure that we can
Lena Stoll: meet the needs, especially of those types of members who we know
Lena Stoll: can't afford to programmatically generate exobil, and who know who need these kinds of tools.
Lena Stoll: in terms of how the tool is used. We've conceived of it as a kind of wizard that guides you through the sequence of necessary steps. One by one you can see a little stepper at the top.
Lena Stoll: And also anytime that you enter something, or you try to complete the steps. The tool will validate for you whether what you've just entered makes any sense, and whether it fits what's allowed in the schema?
Lena Stoll: That's just because, of course. anytime you make a tool that's used by human beings. There's a capacity for people making typos or copy paste errors.
Lena Stoll: especially with such a
Lena Stoll: total task as registering dozens of journal articles by hand. If you've done it before, I'm sure you've made some copy and paste errors, and it's a lot more costly if you have to correct those after the fact. So it's very important to validate inputs early on, which is what we're doing.
Lena Stoll: You can see an example of this actually, on this screenshot in red. Towards the bottom, because I've entered an invalid dui and also, if you're a very keen observer, you might have seen at the top, right. There is a
Lena Stoll: language switcher button. This is what I mentioned earlier about localization.
Lena Stoll: A really important thing that we want to do with any of the new tools that we're building is to make sure that, especially with those languages that we know a lot of our members are much more comfortable with than English. They can be used in those other languages.
Lena Stoll: and the phone could also be navigated using your keyboard.
Lena Stoll: so we're designing it to be accessible enough that it can be used by anyone in the community who actually need it.
Lena Stoll: yeah. So if you look at the slipper at the top you can see that the form asks you first for information on the journal, and then it goes down to the issue level, and then finally the article itself that you're registering.
Lena Stoll: and if you go to the next slide you'll see some of the issue screen.
Lena Stoll: there's not going to be that many surprises there for you in terms of the fields that are represented.
Lena Stoll: You might have noticed already at the top that several titles can be entered both for the journal and for the issue, and then also for the article. That's just because we support multiple languages for titles.
Lena Stoll: Yeah. And like, I said, we're focusing on the key metadata fields and
Lena Stoll: those that are gonna be highest value for
Lena Stoll: making a high quality record and also for the people who use our metadata to have a chance to then discover that content.
Lena Stoll: That's the issue. And then if you go one slide further, you'll see the article level.
Lena Stoll: and you'll be able to see that in this example I've given the article a couple of different titles and different languages.
Lena Stoll: I don't speak so many. So this had to do and there is also a role. Look up already built in if you look closely, you can see for the contributor.
Lena Stoll: you can. If you start entering the affiliation the tool will find
Lena Stoll: the unique identification and the raw database for it. that's something that was quite a crowd pleaser in the grants registration form. And there are
Lena Stoll: more of those kinds of.
Lena Stoll: I guess, quality of life improvements. For using the tool that we know already will definitely need to or want to offer in the form. Once we actually have it, go live for members to use
Lena Stoll: just right now. Not all of them are there yet, because we've been focusing very much on
Lena Stoll: getting a prototype into a state as quickly as possible that we can share it with all of you and with the wider community and get some feedback.
Lena Stoll: If you go one more slide ahead. We'll go to the fourth step at the end of the whole registration process. If, again, if you know the Grants registration form, you'll you'll know what this looks like. We'll be able to give
Lena Stoll: the user adjacent file download of the record that they have just created.
Lena Stoll: The Xml actually doesn't visibly get involved at any point that's just created in the background by the tool automatically and deposited in much the same way that it would be deposited. If the user directly used our Xml Api.
Lena Stoll: the
Lena Stoll: this Json file. So that's one another. One of the things that I said, we know will will want to do. Because it makes a big difference in how useful the tool is. Is that
Lena Stoll: we will allow for users to be able to load those Json files back into the form later and then make changes, which is something that is already the case on the Grant registration form. Just for this very first prototype. We're focusing just on the initial registration part so that we can test that
Lena Stoll: with the community.
Lena Stoll: But we know that editing records after the fact. Especially for general articles, is something that people use metadata manager for a lot.
Lena Stoll: Yeah. So that's just a note on that
Lena Stoll: and actually on that topic, if you go to the
Lena Stoll: next slide. Oh, some people having issues, not seeing slides.
Lena Stoll: I'm just gonna pretend I didn't read that and keep talking if it's working for most. Yeah. Okay. So since I've already used the word soon.
Lena Stoll: obviously, next, questions are, what's coming next. What are the kind of timelines like? I said at the beginning. We went. quite ready and confident enough to
Lena Stoll: To do this live yet and grow into the actual prototype and enter things, and show you how it reacts. So I took the safe route out of taking screenshots. Sorry about that
Lena Stoll: and we can't quite share a link to the prototype yet, either, for you to play around with your sales for the same reason. But like I said, the goal is to get there as quickly as possible. So we're just putting some finishing touches on it. And it's again a very early version, so don't expect to see it in production tomorrow just yet.
Lena Stoll: But of course we'll keep
Lena Stoll: our community updated as we make more progress. We're going to be iterating over the coming
Lena Stoll: weeks and months on
Lena Stoll: early initial feedback that we're going to be getting both internally and then from
Lena Stoll: from some key members of our community. So I just actually, I should say thanks at this point to
Lena Stoll: those of you who are cross-ref ambassadors who have already volunteered to to help us test the prototype will be getting in touch with you very soon. There are also some people who volunteered on the community forum already in the past to be involved in this process, which is great.
Lena Stoll: and then in terms of some future next steps again, if you've used metadata manager
Lena Stoll: recently or not even not so recently, you will have seen that in the Yellow Banner, and the tuss is going to be deprecated. It still says 2023.
Lena Stoll: Right now is the date of
Lena Stoll: sun setting it. But we don't want to rush this while. It's still needed. Because what we're building
Lena Stoll: out as a minimum viable version of this new tool, that's what the Mvp on the slide means minimum viable product for those
Lena Stoll: who aren't so deep in the tech robot hole. Yeah, it's we we don't wanna rush this on. I've put 2024 in here, cause that's probably more realistic. But the idea is that
Lena Stoll: once we've got
Lena Stoll: once we've a bit more formally reached out for community feedback, like we always do with such an important project. And we've iterated on that. And we're getting confident that we have a viable version of this tool.
Lena Stoll: we will be able to put the
Lena Stoll: ghost of metadata manager, I guess. Bit of a Halloween theme here for you. To rest finally and and look to the future.
Lena Stoll: So yeah, if you are
Lena Stoll: one of those people who really resonate with with what I've been talking about and who maybe currently uses metadata manager, or even the web deposit form to register your journal articles, and you want to help us shape this new thing. Then absolutely feel free to get in touch with me. I think the next slide will tell you how to do that.
Lena Stoll: Or not. Okay. That was supposed to be a Thank you. Slide with my email address on it. But I'll make sure to
Lena Stoll: to add that after the fact, I guess. Sorry about that as well. Yeah, it's it's also pretty easy to get
Lena Stoll: But yeah, but I also wanted to say that the the community forum is always also a great place to be if you want to stay up to date with what everyone is doing at crossroads. One of the first places that you'll find out when there's news or something to test or give input on. So
Lena Stoll: shadow for the community Forum. And I'll put my email address in the chat. Look forward to speaking to some of you about this, some more, and for now I think that's it for me.
Lena Stoll: oh, thanks, Jenny. Okay, there it is already.
Lena Stoll: Thanks to you, Rachel, I guess, Leila, there's a question for you in the Q. And A.
Lena Stoll: Yes, okay. We have
Lena Stoll: a question that says. given the driving cross for get publishers to register reference lists, will there be an option to upload reference lists, either in their entirety for passing, or as a list of duis only.
Lena Stoll: That's a very good question. Of course we know that references are a very, very important metadata type, and also one that we've been kind of
Lena Stoll: pushing our members when we discuss their participation reports with them. All that kind of thing to to really consider investing in. So we know that we want to be representing that in this, in this tool, in some way, we haven't really made the definitive decision yet on what the best way of doing those if there will be
Lena Stoll: some way to use our simple text query that we tool that we have to to get Dois for references if you don't have them yet, or if it's better to do them the other way around. I don't think that I would. I have a definitive answer on this yet. But that's exactly why we
Lena Stoll: I'll trying to get this out for community testing and feedback as quickly as possible, so that we can nail these sorts of things down. But that's the kind of thing that we don't wanna make a decision on to early on before we know what's actually most valuable. So if you think you have input on that, then get in touch with me for sure.
Rachael Lammey: And I think we let's I can see there are other questions, but I want to
Rachael Lammey: and I think some advice as well. I want to keep us moving and jump on to the next presentation, just so that we don't run over time.
Rachael Lammey: But we can answer those in the QA. As well, and come back to them. If we've got time at the end, I would suggest, is that right?
Lena Stoll: Perfect? Thanks. Yeah. It's not ready a question, anyway. I think so. I'll just respond.
Rachael Lammey: cool.
Rachael Lammey: Thank you. Okay. So next up we have Eric Hanson from the Public Knowledge project. Or Pkp, who's gonna demonstrate the latest crossref Plugin.
Rachael Lammey: in Ojs 3.4 the Doi work flow has been completely rewritten addressing usability and issues and providing a better overall user experience. So with so many of our members using Ojs extensively, and these improvements are really timely and thanks to the team for sharing them with us and giving us the the opportunity towards the end of last year to test them out. Eric, can we hand over to you.
Erik Hanson: Yeah, thank you. I'll start
Erik Hanson: by sharing my screen if I can.
Erik Hanson: Does not look like I am able to share my screen.
Rachael Lammey: Would you like to have another go?
Erik Hanson: Yes.
Erik Hanson: oh, no, and
Erik Hanson: perhaps fairly typical. Zoom.
Erik Hanson: a live demo of contact slide recently reset my computer. And I unfortunately do have to briefly log off of zoom and restart zoom. I'm terribly sorry about this.
Rachael Lammey: Do you want to? What we can do is we can. We can tweak the order a little bit if you wanna leave, and then we join. I think a couple of us have been hit with zoom updates this morning, which is, of course, another another variable, and all of this. So we'll keep a lookout for you. Add you back in
Rachael Lammey: and and I think that will work. Martin Richman, if you're happy to go next.
Martyn Rittman: Yeah, no problem. I can jump in. So yeah, let me share my screen and hope that hope that all the
Martyn Rittman: it's work.
Martyn Rittman: yeah. So yeah, this is
Martyn Rittman: awesome. Good. So yeah, this is a presentation about a new Api endpoint that we that we have and I'm gonna demonstrate it via a Jupyter notebook. I realize this is in python, and some of you might be might be not familiar with python. Don't worry. I will explain and point out the the most relevant bits as we
Martyn Rittman: as we go through. But basically, this is looking at different ways that we can, that we can look at cross-ref metadata. So I'm going to talk about relationships. Firstly, how you
Martyn Rittman: can get hold of relationships, and where, how we will combine those into one endpoint in the future. So if you are familiar with python. All I'm doing here is using the requests library to query, Apis, here's the endpoints. If you'd like to try this out.
Martyn Rittman: then then you can go to to this this URL, which which has the the endpoints, and I'll give you a few more pointers at at the end for that I've also I'm not running this off a Co. Lab notebook, but I have a Co Lab notebook, and I'll share the link for that. At the end. As as well. So yeah, we're just gonna start the the notebook with a few useful functions which are to show you the URL, that we're querying. See that in a moment. And then this is this is the function that does the the work.
Martyn Rittman: And it it it. Queries some URL, and it expects a Json output. So this is Json is the the format of the data that that gets returned from our Apis.
Martyn Rittman: So as we're we're talking about just now very timely. References are very important, and many of our members send us references. And what we can. What we, what we do at Crossref is display those through a works endpoint. So each item has an entry. And you can query the works endpoint. Using this URL. So you know, Api dot crosswift org slash works. And then we have in there this
Martyn Rittman: filter which say, it says, does this item have references or not. Just give me the ones with references.
Martyn Rittman: And just to give you examples, we have, you know, 8 references for this, do I? 80, 90 for this? I don't know what this this is. Maybe it's a book or something, but 424 references. II feel sorry for the the poor production people who who have to go through all of those. What do these actually look like in in Json?
Martyn Rittman: well, this is the this is the Json list of references. I just pulled out the the reference part of of the of the response.
Martyn Rittman: And we can see that this do I? Here is citing a number of of things, and this is this is one of them that I'm highlighting here. It has a doi. It also has the title, The authors and we've got this unstructured references as as well. You don't have to pass references to put them into our
Martyn Rittman: To to deposit them with with us. You can have just unstructured text like here. You don't even need a doi. We will try and match that for you. So you can see. Just kind of, you know, more examples with similar kind of information.
Martyn Rittman: So that's that's references.
Martyn Rittman: There's another way that you can add links between outputs in in slightly more descriptive ways.
Martyn Rittman: And that's using the relationships.
Martyn Rittman: Part of our schema. And
Martyn Rittman: again, I'm going to query, the works endpoint? Gonna query the same endpoint. But instead of saying, has references, we says, has has relations?
Martyn Rittman: Does does it have a relationship? And that's that's run nice and quickly, thankfully, this is always always risky doing a live demo. But anyway, here's just one example, and we have
Martyn Rittman: here we have the type of relationship. That we just pulled the relationship part out of the the Json response.
Martyn Rittman: And then it says it says what the relationship is to as well. And this is just an an identifier says it's a doi. You can add other types of identifier in there as well.
Martyn Rittman: And we say who it's asserted by so subject means that it's asserted, asserted by
Martyn Rittman: the the the member that deposited this metadata. If it said object, then it would have been asserted by the member who deposited the metadata for the related item.
Martyn Rittman: So it's you know, there's 2 sides to a relationship, and one. This happens in life as well. But you know, 1 one person says one thing, one person says another thing. And as you know, they don't always agree. Here's just a few more examples. So we have reviews. We have comments, then these are mostly reviews. This is one with, an article with a preprint
Martyn Rittman: and we can see that, you know. Some of these were asserted by the the member who deposited the the object, the the metadata, some of them were asserted by for example, this one was asserted by the the member who deposited the comment and said, it comments on on this, and we match up in our as has already been mentioned, we we match up the reverse relationship here. So that's kind of nice. But you might notice that this output looks very different from what we saw before, with the references different kind of
Martyn Rittman: of metadata available.
Martyn Rittman: So I mentioned briefly that you can link to things outside of Crossref.
Martyn Rittman: We have a project called Event Data, which, where we go and look for relationships.
Martyn Rittman: From crossraf duis that are kind of, you know, mentioned around the web. So, for example, on Wikipedia hypothesis, annotations, we look on on Reddit, and just kind of blogs and websites
Martyn Rittman: and
Martyn Rittman: I'll just show you one example here. We're looking at specifically at Wikipedia. And now the the Eagle light among you might notice that. The event. Data. Api is being closed down from the end of next month.
Martyn Rittman: This is because we will continue to collect events. But we want to be able to. We want to focus on the new endpoint, the relationships endpoint as you'll which you'll see in in a moment. And the best use of our resources is to
Martyn Rittman: stop is is to stop with event data, put all of event data into the relationships, endpoint and make that usable for for the users that that are doing that. So if you are using event data,
Martyn Rittman: you'll want to look at the
Martyn Rittman: at the relationships endpoint as as you ever in the next few weeks.
Martyn Rittman: So this is an example of an event, and you'll see again. It looks very different to the references. It looks different to the relationship metadata that we saw.
Martyn Rittman: But essentially, we've got the same kind of information. So we've got an identifier for the subject. In this case, it's a yeah. URL Wikipedia page.
Martyn Rittman: We have an identifier for the object, which is a crossref. DO.
Martyn Rittman: And we say how these 2 things are linked together. And and this is as as as a reference. So you've seen here. There's 3 different ways that we essentially deliver the same metadata
Martyn Rittman: and you know we've been looking a great deal in the, you know, in the past few few months and years at the research nexus and that doesn't really preference any kind of item or any kind of relationship. And so we said, Well, why don't we reflect that in our Apis
Martyn Rittman: and provide all of the relationships that we know about through a single endpoint and in the same format. And this is what we've been been building for a while now.
Martyn Rittman: And, as I said at the at the beginning, this is the this is the URL, and I'm just looking for, you know, a single day. So we've got. We've got a number of of filters time filters, for example, on the on the output. And you see, on this day there were about 2.4 million relationships found.
Martyn Rittman: I'm not going to show you all of those. But this is just one of them. And
Martyn Rittman: again, we've we've tried to pair it down to the the minimum kind of useful information. And we'd love feedback as to whether this is sufficient, whether we need more, whether we need less and what would make this useful for for you to use.
Martyn Rittman: And so we have a subject. So this relationship comes from across F doi, and in this case
Martyn Rittman: is going to an organization.
Martyn Rittman: So this, I can tell you, because I've I've looked at this way too often, is is wily, and it says that this doi was published by Wiley, essentially and this information was asserted, instead of just saying subject or object, or or a word, we're using a raw identifier for crossref.
Martyn Rittman: So basically, crossref is asserting that Wiley is is permitted to to manage the metadata record of of this doi
Martyn Rittman: So in the first instance, we are focusing on data citations which have been mentioned quite a number of times already. So I'm I'm really happy to to have heard that it kind of
Martyn Rittman: hopefully, I don't need to give too much motivation for why data citations are interesting and and important.
Martyn Rittman: And again, we're going to query the relationships endpoint. We're going to look for things that have the type data set. And we're just going to look for a single day and see what the
Martyn Rittman: what we find.
Martyn Rittman: And we find. Actually, there were a hundred and 147 data citations, or
Martyn Rittman: found on this day. Now, this. What this means is
Martyn Rittman: the subject type data set. This is with a capital D is, the is is used by data site. So these are actually not data citations deposited by crosswf members. These are data citations being deposited by data site members. They very kindly pass that information on to us, and we're able to make it available through the through our endpoints. And you know we do that reciprocally as well.
Martyn Rittman: And let's just have a look at the, at the output there. So we can see.
Martyn Rittman: You know, there's various relationship types which are used. So you know this.
Martyn Rittman: this? This, this doi here. So this one here is is metadata for this crossref. Doi
Martyn Rittman: this data site doi is posted content, which is
Martyn Rittman: So yes, this. This is across Fdi, which is posted content. And
Martyn Rittman: it's cited by this this data site Doi, which is in Zenodo, and and so on, and and so forth.
Martyn Rittman: So of course I mean II don't know whether doing a live presentation on this make makes sense. But you know, the idea is that this is machine readable. And if you want to look up more information about a doi, you can just go to our works, endpoint and and retrieve the the metadata for that. This is really focused on the, on the relationships.
Martyn Rittman: It's like I should have short on the output for this one, anyway.
Martyn Rittman: you can. This is. This is why I'm not convinced is going to work, because this query has been taking rather a long time. At the moment. But you can query for everything which has been registered by data site.
Martyn Rittman: and the the output I've I've done. I've done a short kind of put the output here, but you know this is this is the output that you will see. There's just to to show you. You know, more kinds of queries that you can make
Martyn Rittman: and so I'm not quite sure how I'm doing for time here. But
Martyn Rittman: yeah, we can. We can let people get to the end. What else?
Rachael Lammey: in the. But yeah, just a about a minute left be great. Okay? Fine. Yeah, so just very, very quickly. Then you can. You don't have to look at a doi. You can look at orchids.
Martyn Rittman: You can look at organizations you could. There's funding metadata in here.
Martyn Rittman: So yeah, this is, says the orchid was an author of of that. This
Martyn Rittman: we can see, that cargo has has deposited 50,000
Martyn Rittman: references, and you know we've got funding information in here as well. Sorry to kind of blast through that very quickly, but I will put this I will put this colab notebook link into the the chat, and you can have a look and have a look by yourself.
Martyn Rittman: Yeah, thanks. Thanks a lot for for your attention.
Rachael Lammey: Awesome. Thank you very much. That was really interesting.
Rachael Lammey: there's the link to the notebook for anyone to have a look at. I am really conscious of time. Maybe one question
Luis Montilla: Luis, you want to take, and then we can get to the other ones in the chat. Sure, alright, perfect.
Luis Montilla: There is one question. Maybe you can answer very quickly.
Martyn Rittman: yeah, so yeah, is event data going to be available in relationships. Api, from day one. The answer is, actually, probably not. There will be a a gap we have committed to making all of event data available by the end of January 2024.
Martyn Rittman: but we we, you know, event data for those of you who've been using it has been unstable for quite some time, and we've decided that it's better to focus on something new
Martyn Rittman: and stable, and there may be a a gap in which some events are not available. We've really focused on data citation because we know that that's a very important use case. And all of data site,
Martyn Rittman: all all of the data citations that we know about will be available. From day one. The rest we will add. Gradually over over time.
Rachael Lammey: That's great. Thank you? No, said you can. There's a few other questions in the chat that you can pick up. Thank you, Eric. Should we try again?
Erik Hanson: Yes, fingers crossed. Thank you so much for moving things around for no worries.
Rachael Lammey: Yep, we can see your screen
Erik Hanson: perfect. Okay. So, jumping back to a few minutes ago. But those of you who are unfamiliar with open journal systems or Ojs, that I'd give just a brief
Erik Hanson: overview of what it is. It's an open source journal management and publishing platform.
Erik Hanson: It encompasses a submission workflow, peer review as well as the production workflow.
Erik Hanson: And it's currently in use by more than 30,000 journals worldwide and today I'd like to share with you a little bit about the new doi work flow in the latest release. 3.4, which came out in June ninth. But in order to provide a little bit of context around that, I'd first like to show you a little bit from the previous version 3.3
Erik Hanson: set up. Why these changes are so big and helpful, especially for people who are managing lots and lots of dois.
Erik Hanson: So for those of you who are unfamiliar with Ojs. This is the home screen view for. And then editor would log in. I just want to show an example of
Erik Hanson: what's some of the pain points are when dealing with the Dois in the previous version. So to start with, one of the major ones are around doi creation. It's spread out throughout many different places throughout the application. So, for example, if we were to pull up
Erik Hanson: this published article, currently I only have a article, do you enabled? But I'll show an example of where all of those would go. So
Erik Hanson: this is the kind of publication tab for
Erik Hanson: a published submission. The article Dui would be under here
Erik Hanson: under the identifiers tab. If you have a galley, dui, it would be separately under here, and the issues would be yet under a different tab entirely.
Erik Hanson: Another pain point that this brings about is, you can see from this big red Banner. This version has been published and cannot be edited, and this often happens that an article will be published. This is especially prominent in with preprints
Erik Hanson: before a Dui has necessarily been assigned to it.
Erik Hanson: and this has previously been impossible in Ojs. And encourages bad practices around things like unpublishing it to update the metadata, then republicing it.
Erik Hanson: Highlight. One other pain point here
Erik Hanson: is around the previous and doi pattern, and this is what we call the default. Doi suffix generation in Ojs. 3.3 and previous.
Erik Hanson: If you come to assign the Doi, you'll see this warning, which says, you cannot generate a doi until this publication has been assigned to an issue
Erik Hanson: to just quickly show at a glance what that entails. Going to the Dui settings for this version.
Erik Hanson: and in Ojs. 3.3 and earlier, we use a pattern-based suffix generation which does contain semantic information about the item in question. The most common one is for articles, and it includes information about the issue.
Erik Hanson: The volume number Ids inherent to it from Ojs itself, and this is often very problematic, because the Doi cannot be assigned to an item until it has been assigned to an issue. And this is
Erik Hanson: often very problematic, because maybe an item shouldn't be assigned to an issue yet. But you would like to have a dui right. You shuffled around, and you want to be able to assign it, doi. It's part of the pre-production, so it's a little bit of background on some of the kind of pain points of Doi
Erik Hanson: generation
Erik Hanson: which brings us to
Erik Hanson: OJS. 3.4 and the same view here just as a starting point.
Erik Hanson: So
Erik Hanson: I'll do a quick walkthrough of the process of setting things up as well as show some of the highlights of the new workflow.
Erik Hanson: So first of all, you'll notice Duis are featured very prominently on the sidebar here. So one of the major changes is that Dois are now a core part of the application. Previously they were a separate plugin, which kind of limited the amount of integration, deep integration into the application that was possible.
Erik Hanson: and the Crossraf Plugin and any of the other registration agency plugins are still plugins, but this new architecture allows them to be more deeply integrated into the application. And I hope, as they go through some of that today, you'll be able to see some of that
Erik Hanson: to start with.
Erik Hanson: Show you what some of the settings look like. Just to provide some context. duis can be enabled or disabled as part of the distribution workflow
Erik Hanson: globally here.
Erik Hanson: next up. It's very similar to previous versions items with the Dois. Currently, I only have articles selected. This also varies across the different
Erik Hanson: software applications that Pkp makes for one for monographs and one for preprints. But it's roughly the same idea.
Erik Hanson: One new thing here in particular is that by default. Anything that O. Js can create a dui for is possible here
Erik Hanson: of note is the article, galleys
Erik Hanson: and this is usually in the most default context that publish Pdf cross-ref for the cross-ref Plugin. This option is disabled.
Erik Hanson: and this can be configured for other registration agencies. If, say they didn't take issue Duis, for instance, and
Erik Hanson: potentially more applicable, is for monographs, if different services do or do not take Chapter duis, or that don't have the capability to distinguish between those types of things.
Erik Hanson: and I'll show what that looks like here.
Erik Hanson: next big thing is the automatic dui assignment.
Erik Hanson: the philosophy around this was just to be able to generate Duis as early as possible so that they're there as part of the production process part of the layout process.
Erik Hanson: It's gonna be done on reaching the copy editing stage, which essentially means as early as possible
Erik Hanson: on publication or never, in other words, manually and when we looked at the pain point from Oj.
Erik Hanson: What that
Erik Hanson: kind of has bearing on for this is that you needed to have assigned things to an issue
Erik Hanson: that is no longer the case. The default suffix generation now creates
Erik Hanson: a unique 8 character suffix. And this is a pattern we took from inspiration, from a data site tool
Erik Hanson: that would create an 8 character suffix, and it includes a checksum digit so it can be checked programmatically to make sure there are no typos in a similar way to iss ends or Isbn's
Erik Hanson: so one of the other big wins is because it's a unique character suffix. It does not contain any semantic information, and there is no temptation for editors or journal managers to want to use
Erik Hanson: the duis to convey any sort of semantic information that they might want to change later. For instance, if the name of the journal changes, they won't want to change their dui subjects because it doesn't have any information about that, to begin with.
Erik Hanson: next bit is all information about the registration agencies has also been co-located here. So the name of the game with a lot of these changes is co-location. So, wanting all the settings to be co-located as well as the actual doi management itself.
Erik Hanson: So we go here.
Erik Hanson: We can check which registration agency. We'd like to rich registration agency Plugin we'd like to work with right now. I have crosswift setup.
Erik Hanson: Let's see Crossword Demo, and that makes the most sense. But all of these settings are co-located here.
Erik Hanson: Automatic deposit is still functional. and all of the settings are here, along with some added context about the username and the roles for setting those up.
Erik Hanson: Go ahead and enable that.
Erik Hanson: and then move on to the new doi manager interface. So this interface here will be more or less the same, regardless of which registration agency is used. If a registration agency Plugin is enabled at all.
Erik Hanson: and this will be the same across all the applications. So this was really done in an effort to
Erik Hanson: unify the way that journal managers and editors can work with duis.
Erik Hanson: So a few things I'd like to highlight around this
Erik Hanson: are the basics of doi assignment as well as some of the quality of life things. So some of the first things that jump out are the
Erik Hanson: red badges here? These will usually
Erik Hanson: show the top priority things that a journal manager would want to see when they come to the screen, and this includes things like whether items still need to be assigned as Dois
Erik Hanson: once items have been published, whether they are are unregistered as well as if there are any errors in the registration process.
Erik Hanson: so we can filter things based on
Erik Hanson: these types of things. So you want to see all of the items that need duis
Erik Hanson: that includes everything, because nothing has doi assigned. At this time.
Erik Hanson: There is an explanation for what all of these
Erik Hanson: individual statuses mean as well as the filters. that can be updated or that can be viewed. If you are looking here at a later time.
Erik Hanson: also impossible to filter by
Erik Hanson: issues. And if you're using an issue-based workflow can manage everything
Erik Hanson: there.
Erik Hanson: One of the other big improvements in terms of the workflow for time. I didn't show an example of this in the Pain Point section in 3.3, but the ability to do bulk actions so
Erik Hanson: to paint a picture of it. Imagine you had 300 items that you needed to assign Dois, or reassign or re-register. Previously you had to tick all of these manually, and this was just a quirk of the design of the forms.
Erik Hanson: We now have bulk actions, and this is where the heart of a lot of the functionality is we filtered for the issue we want.
Erik Hanson: We select it all. And now we'd like to assign some duis to these.
Erik Hanson: and we can now see that the status of these move from needs do I to unregistered
Erik Hanson: Dois can be edited under this expanded view. If you have more than one dui for an item. You are using galley duis, or if you're working with monographs and have more
Erik Hanson: types of items that have duis, those can all be managed here.
Erik Hanson: It can be edited here as well. and once you're ready it can be deposited. So I'd also like to just take a moment to highlight this as the
Erik Hanson: new type of suffix. It is still more or less human, readable. We tried to strike a balance between it being easy to
Erik Hanson: share and read without having.
Erik Hanson: without being too long
Erik Hanson: and still maintaining enough unique
Erik Hanson: possibilities. So the current pattern we have.
Erik Hanson: there's a bit high. 1 billion different unique combinations that are possible per prefix
Erik Hanson: on the off chance that we do run into duplicate issues. A new soft fix can always just be generated for that item, although that's quite unlikely
Erik Hanson: before showing the deposit workflow. I want to show you how the automatic workflow works. So I gave a brief
Erik Hanson: an example of that
Erik Hanson: the previous one. I will
Erik Hanson: show it for this as well. So I'll take an item here that has not yet been through the review process, but will pretend
Erik Hanson: for moments that this has been accepted for publication.
Erik Hanson: record that submission. And now it is moved into the copy editing stage. If you recall, we've now set up dos to be assigned as soon as an item reaches the copy editing stage.
Erik Hanson: So if we go over to the Dois tab it loads up.
Erik Hanson: We should now see that this item that we were just looking at now has a doi assigned. This is something that was not previously possible.
Erik Hanson: and ends up, causing a lot more headaches than it might initially appear. Not having do I. Assignment tied to any semantic information about Ojs metadata is a huge thing for us, and consequently
Erik Hanson: creates fewer problems downstream for registration agencies like crosswf. As a final bit. I'd like to just show the registry
Erik Hanson: registration process. One other pain point from previous versions was that
Erik Hanson: when you were trying to submit multiple items to be registered, they would often time out, and it was not always clear
Erik Hanson: what the threshold for that was. The registration process has been reworked to use a jobs-based system. So for each of these items that we want to
Erik Hanson: deposit, they will now be queued in a jobs queue. And so if we go here, what that means, we go to deposit them.
Erik Hanson: Ui feedback should be instant, and they've been queued for deposit.
Erik Hanson: and the Xml generation and all of that slow process will happen one at a time. and as those are updated, please refresh the page. We should see.
Erik Hanson: once those processes have finished, that
Erik Hanson: the deposit will be successful.
Erik Hanson: I won't make you watch that, because that is a very long and slow process sometimes, which is the whole point of moving it into a background job.
Erik Hanson: And I believe that is all that I wanted to share with you today.
Erik Hanson: Thank you so much.
Rachael Lammey: Great thanks, Eric. We got it ruling in the end. So I think there's a question that's just come in.
Erik Hanson: Yes.
Rachael Lammey: from Tom. So yeah, this is the automatic assignment.
Erik Hanson: Yes. Copy. The way it works is copy edit. The copy editing stage would be the first opportunity
Erik Hanson: for things to be assigned. If, when it moves to the production stage, it could also be assigned.
Erik Hanson: And so the idea is that this accommodates work flows where editors and journals
Erik Hanson: either use or do not use the copy editing stage, but one way or another, it will have to go to either the copy, the editing stage, or the production stage before being published, so the automatic assignment will, it will attempt the automatic assignment at both of those stages. And this is also true if the legacy pattern generation
Erik Hanson: is also still in place, because obviously that would require an issue to be assigned. So it will first try at the copy editing stage, if it skips, that it will try at the production stage, and if it skips that.
Erik Hanson: or if it's still not possible, it will try again on publication, so it will try as many times as possible. But we'll rewrite steelies if they're already created. That answers your question.
Rachael Lammey: Awesome. Thank you. I'm conscious of time. There's another question that's just come into the chat, and I think probably my question is around just where people can get information on upgrading to Ojs 3.4, so they can take advantage of a a lot of improvements. I think it'll just really help kind of ease a lot of those kind of pain points. So yeah, appreciate it. Thank you
Erik Hanson: absolutely. I'll put my email if anyone has any questions, and I will also link out to the release post about Ojs 3.4, and I'll add that to the chat.
Rachael Lammey: Excellent! Thank you.
Rachael Lammey: So at this point I'm gonna hand over to
Rachael Lammey: Luis Montier, who's been
Rachael Lammey: who's been leading things on the technical side.
Luis Montilla: Sure. Oh, can you share my slides for me, please? Yes, I can indeed. Let me just grab those. Thank you.
Rachael Lammey: Oh, sorry! 2 s.
Rachael Lammey: Sorry I've got these.
Rachael Lammey: I
Rachael Lammey: I'm sorry. I just need to jump through to your slides.
Rachael Lammey: Yeah, if you want to go ahead and introduce your session, then, sure, yeah, I will. I will. I'll catch up with you. Perfect. Thank you very much. Thank you. Everybody for being here. My name is Luis Montelia. I'm the technical community manager at crossroads.
Luis Montilla: And today I will be talking about well, giving up a very basic introduction to the crossroads Api.
Luis Montilla: which will start in the minutes next one. Yes, perfect.
Luis Montilla: Next one, please.
Luis Montilla: So this presentation will be about Apis. But more importantly, it will be about the possibilities that the community has to interact with the past network of relationships between research objects, and which is what we call the research nexus
Luis Montilla: in more practical terms. We are talking about metadata, which are the basically the descriptors of of research objects and how we can establish relationships between them. Next one please.
Luis Montilla: So we make this meet today openly available via our Api's and our public data files enabling the people and machines to incorporate it into their research tools and services, and at the same time, we collect and we operate distributed this metadata
Luis Montilla: as part of the ever-growing research nexus. It's safe to assume that not everybody understands what an Api actually means. They're forced the purpose of this presentation. It's to provide a quick introduction to the use of the crossroads. Api.
Luis Montilla: So if we see the slide, we see, then a an Api is an software intermediary that allows 2 applications to talk to each other, and Apis are often compared to a weather service, facilitating communication between customers ordering items from a menu and the kitchen producing those items
Luis Montilla: next one, please.
Luis Montilla: So we make this metadata open through our rest. Api. You can visit the URL to access our documentation. I also shared the link in the chat and the presentation before and then you can use this to perform chorus directly from your web browser.
Luis Montilla: There is no registration required. Cross Ref. Once again, it's committed to providing an open and as anonymous as possible access to scholarly metadata
and keep this URL at hand for the next examples. Please.
Luis Montilla: however, we do have some recommendations and etiquette suggestions to follow. If you wish to retrieve metadata
Luis Montilla: first, by adding your email address to your request, we can contact you in case of issues. then, additionally, we redirect this request to a specific polite.
Luis Montilla: a pool of servers.
Luis Montilla: These servers are generally more reliable because we can more easily protect them from misbehaving scripts in contrast with full anonymous requests.
Luis Montilla: And then there is a third alternative, especially if you are using our rest. Api for a production service
Luis Montilla: that require high predictability this option is to consider using our our paid plus service which which provides you with an authentication token that directs you to your request
to a pool of service that are extremely predictable.
Luis Montilla: Next one, please.
Luis Montilla: So for the specific examples, I'm going to show you next. I'm going to use postman, which is an Api client, and we don't endorse this app, but we acknowledge that it is widely used, and it provides a set of functionalities that makes metadata retrieval much easier.
Luis Montilla: However, you can also execute these words directly in your web browser once again. In most cases your browser will display this quarter results as in adjacent format.
Luis Montilla: However, in some instances you might need to install a browsering extension
Luis Montilla: next one, please.
So, before moving on, I would like to take a second to establish some basic vocabulary
Luis Montilla: that will that you will encounter throughout these presentations. So the text that you see here that at the top represents a query. The first part that you see color in yellow indicates the server.
Luis Montilla: So this identifies the entity providing the service, and all of our crossraft-related cores will share this common route. Then you have the endpoints. This is a key term that we will use to identify the digital locations that receive a connection.
Luis Montilla: And I will show you soon the other end points that we have available to the general community.
Luis Montilla: And then, finally, we have the the parameters you can identify them as being preceded by a question mark.
Luis Montilla: and then they follow the notation of having a key and a value.
Luis Montilla: So, for example, in this specific example, you can see a query that has the the mail to parameter in these parts basically allow you to specify resources and also to perform all directions such as in this case identifying yourself
Luis Montilla: next one, please.
So if we check the documentation. We'll find a list of different locations for the endpoints that our Api contains. Data of interest
Luis Montilla: in this presentation. I'll show you some basic examples of the data that you can retrieve using some of these. Perhaps you know this in the previous slide that I was using the funders endpoint but we have endpoints specifically for journals, works across rough members and several others.
Luis Montilla: Next one, please.
Luis Montilla: What? Now, let's explore some basic examples. We'll start with Funder to article relationships.
This is interesting because funders do not automatically know when the work that they have funded is polished
Luis Montilla: and it. But it's also essential for reporting on the impact of brands. And then finding this information can be challenging through other means. Because of publisher software and institution institutions do not systematically report it.
Luis Montilla: Next one, please.
Luis Montilla: I'm going to. This is not going to be a live demo. This is going to be through done through screenshots so as you can see here. We include in the top part the string that contains our server. The endpoint that I was mentioning before the funders endpoint
Luis Montilla: and other parameters. In this specific case I'd like to start with the a very general search, so I include the mail to parameter to make a product request, and I add a query with the text, German Research Foundation.
Luis Montilla: next one, please.
Luis Montilla: So when you submit this query. You will receive best a status code. In this case, everything it it's okay. And then we luckily we can see how many items we are retrieving with this query, which I'm highlighting here you can see that we are retrieving 4 results
Luis Montilla: next one, please.
So if we examine hopefully, it's very. They had have a good resolution. But if we examine the output in detail, we will notice that our peripiers, as part of the field, alternative names and organization that we are looking for appears on top
Luis Montilla: and then from here we can take notice of the Id number. Then can you use this to refine, refine our queries next one, please.
Luis Montilla: So, for example, if we use this Id as part of the an additional path level in our funders endpoint.
Luis Montilla: we can retrieve organization specific data. For example, here you, we can see that almost 200,000 works have the the Grf as part of the re funding organization
Luis Montilla: next one, please. Thank you.
Luis Montilla: So we can take a few seconds. And in case you want to try this, or if, of course, if you're watching the recording, you can post a presentation. So please visit this URL, you can scroll down to the Funder section.
Luis Montilla: Click, get. And please remember to add your email to the mail, to field and finally include the any funding organization that you wish in that query field.
Luis Montilla: Let's have a few seconds.
Luis Montilla: Okay, next one, please.
Luis Montilla: So this screenshot shows one possible result. Please notice that you should get the status code 200, indicating that your query proceeded correctly, and what it's called here. The response body contains your data.
Luis Montilla: Next one, please.
Luis Montilla: If you're pasting these queries directly in your web browser at the search world, it will likely look like this the latest versions of fire folks and Chrome and several others should let you visualize this Jason file.
Luis Montilla: I was doing some testing safari, and then, if it was one, they want required to installing an extension. Consider this
Luis Montilla: next one. Thank you. So we can pro of this output a little bit more by adding additional field queries. Once again, these are listed in our documentation. Some of these accept text rings, some others are numbers, the others are Boolean expressions, meaning true or false.
Luis Montilla: and of course they can be combined different ways. Next one, please.
Luis Montilla: So, for example, here, let's imagine that we are interested in knowing how many of the selected organizations funded journal articles are publicly available.
Luis Montilla: So in this case we can add one filter that includes the type element. In this case, we're setting these to journal articles.
Luis Montilla: and we are also adding the filter that asking if this contains a full text element, and we are setting this to false
Luis Montilla: next one, please. So you can try combining some of these. I'm showing you here the example that I just used.
Luis Montilla: And then, of course, we can combine these fields more. So, for example, we can also explore, we can query the specific
Luis Montilla: awarded grants that is available in the in the work list.
Luis Montilla: Next one please
Luis Montilla: of, we can also facet aggregate data using the facet fields. In this case, we can use this. For example, to aggregate the results in terms of the publication year
Luis Montilla: next one.
Luis Montilla: And here I'm showing the example. In case you want to replicate these examples.
Luis Montilla: and what with this slide that will finish my presentation, feel free to contact me, I will let my details in the chat and hope. This presentation was kind enough to anyone who was not aware of how to use an Api before. Thank you very much.
Rachael Lammey: And, Louise, that was excellent. Thank you very much. And again, just to reiterate, we'll share the slides and the recordings so that you can. You can dig into this more
Rachael Lammey: Louise joined the the team at Crossraf a couple of months ago. So if you enjoyed that demo and there'll be loads more to come in future and just help people get to to grips with how to use the the crossref metadata.
Rachael Lammey: I'm
Rachael Lammey: again questions in the charts or in the Q. And a, and we'll pick those up. In the meantime, I'm going to keep screen sharing and I'm going to talk just really quickly about the the work that we've been doing with the with the data that's come from retractionwatch. And Martin Eve is going to help me out whenever I get when it as. And when I get stuck.
Rachael Lammey: the
Rachael Lammey: just for for context, in case you weren't aware, crossraf acquired and opened the retraction watch data in the middle of September. And I've linked to the blog post that describes that in more detail. The other thing I will do as well is for the context of why this information is important, etc. We covered in a community in a community session
Rachael Lammey: last month as well. So we'll share those which will give you lots more context than we have time to do today.
Rachael Lammey: There are lots of things that we know and expect our community to do with more comprehensive complete information on retractions? So
Rachael Lammey: we wanted to make the data available. A, you know, in a very simple Csv format, but also via our labs Api, so that people can can start to get to grips with it early doors.
Rachael Lammey: I'm so, as I said, as well as the
Rachael Lammey: Csv format. We made the our more more accurately. Martin made the data available via our labs. Api.
Rachael Lammey: What I mean when I say the Labs Api is that it's it's an environment where we test stuff out.
Rachael Lammey: adding new data and new representations of existing data. And I think the main message of this presentation is. It's where we'd love some feedback on how we are displaying and representing the the data. There's a little snapshot of it over to the the right hand side of this. This slide
Rachael Lammey: As Louise mentioned, we asked you to use a meal, too. So your email to
Rachael Lammey: when you're accessing the the data
Rachael Lammey: and the information is available. As you can see via the Via. The works route in the in the Labs Api.
Rachael Lammey: I've pulled some of the information out just to try to make it a little bit clearer. Martin, I'm happy again. You can talk to the pieces that I've missed. But what sort of jumped out to me is someone who uses and is really interested in this is that we've got a couple of fields here, so we've got the the raw Id of the center for scientific integrity. Who are the folks behind the retraction watch data. So I think that's a that's a
Rachael Lammey: a nice thing. Because again, we've got rural identifiers. We want to be able to use those 2 uniquely and accurately identify institutions. And we've got
Rachael Lammey: we're trying to be really clear about who made the about who made the assertion that an article has been retracted, because in many instances we've got a retraction being asserted by retraction. Watch that isn't currently reflected in the publisher metadata. And again, of course, we really hope and expect that that will that that will change over time.
Rachael Lammey: and we're thinking about how we model retractions full. Stop.
Rachael Lammey: so, said Martin, implemented the workflow and crunched the retraction watch data to make it available via these routes. So thank you very much. But do you want to say more about the current implementation and the plans going ahead.
Martin Eve: Sure. So
Martin Eve: there are some limitations around what we've got at the moment. So, for instance, it's not easy to do filters in our Labs Api system. So this should not be at this point a full replacement for the production Api, and and you shouldn't expect the same same stability or performance. What it does do, though, is, let us test whether the information that we're representing is in a format that's of use to our community.
Martin Eve: So what I would urge is, if you are someone who's been making use of the retraction watch data, and you're thinking about using it in an Api format. If you could have a go at using the Labs Api, and seeing whether it meets your needs and giving us feedback on what's missing, what you need. What's there? What's good? That would all be incredibly helpful for us in thinking about how we move this through to production
Martin Eve: at a later stage.
Martin Eve: Is that is that enough, Rachel? I'm not, as I'm not sure what else I can add there. At this point
Rachael Lammey: I think that
Rachael Lammey: I think that that's more than enough, and we will again. We'll pass on information on how you can get in touch with us about that and I know that lots of people have already. So I think that's really important. And again, please feel free to jump into the chat or QA. And ask us questions about the data, and we'll also post a link to the the webinar
Rachael Lammey: from a couple of weeks ago to do that. So we just want to flag this up. This is an area where we're really keen for for feedback. So
Rachael Lammey: so so do go ahead and give us that
Rachael Lammey: I am.
Rachael Lammey: I am going to. So, Martin, I'm gonna leave you to your own devices for the next demo. So and so you've been doing work to analyze the present preservation status of content registered by crossref members. So. I'll leave it to you to to share your analysis and your your thinking around that. Now, thank you.
Martin Eve: Thank you very much. Just bear with me a second while I try to work out. I'm gonna share the correct monitor, or whether I'm gonna show everyone all my emails.
Martin Eve: try that one.
Martin Eve: Have you got presentation there, Rachel, or presentation and no emails? That was a good guess. Then, on the on the one of 3 notice. Okay, thanks everyone. So I'm gonna talk today a little bit about the state of digital preservation and a study that we conducted across 7 million dois.
Martin Eve: this is a really important aspect of crossrefs. Practice that sometimes goes under remarked upon, which is that for crossref to provide a stable linking service between different platforms, we need to know that material has been safely, digitally preserved.
Martin Eve: Why is that? Because if the original source goes offline, where's the doi going to end up pointing, if there's no digital preservation source to which we can redirect doi, then actually, the persistence of our yeah Urls is limited to the lifetime of of an original
Martin Eve: Http endpoint.
Martin Eve: So when you join Crossref, one of the conditions of membership is that you will make best efforts to ensure that your material is safely, digitally preserved.
Martin Eve: But we don't know what proportion of scholarly objects assigned to do. I are actually adequately preserved in a recognized dark, archiving system, like clocks, locks, portico, or even the Internet Archive.
Martin Eve: We don't really know how stable those preservation systems that underpin the persistence of these persistent identifiers is at the moment we haven't yet had a mass extinction event of of Dois, or anything that has has really used us to use those systems en masse.
Martin Eve: We don't know which actors of our membership are behaving well on this theme. Who does digital preservation well and who does it badly?
Martin Eve: We don't even really know in the era of digital who should be doing this? Is it libraries? Is it publishers? Has that changed since the print era? Should it be both of those parties.
Martin Eve: and most importantly, perhaps with a slightly apocalyptic tone. Again, is it already too late?
Martin Eve: Is a vast suite of material that is not preserved, that we're now going to struggle to get into some preservation mechanism. At this late stage in the day.
Martin Eve: So I set about building an item level preservation database system that would allow us to iterate over a sample of Dois, and to figure out where these things are preserved.
Martin Eve: There's an existing system called the Keepers registry that performs a similar function, but it doesn't have an Api with open use that we could just use to query at scale
Martin Eve: a large number of Dois. It also looks at the container level.
Martin Eve: so it will tell you. This issue and this volume of this journal are preserved, not whether this do I is preserved.
Martin Eve: So I had to build something that would translate between those layers. But I built a system that incorporates the the archives that you can see on this slide share. So Carrioniano, which is predominantly southern Latin American material clocks controlled lots of copies, keep stuff safe. Archive.
Martin Eve: have the trust Internet Archive locks. The more general version of clocks, pkps, private locks network, which is a system that Pkp implemented to help open journal systems users ensure their material is safe
Martin Eve: at Portico, another dark archive and the Oakall scholars portal in Canada.
Martin Eve: I also needed some way of figuring out how to score members and how they're doing on digital preservation. It's all very well to just say, this is what's going on. But you need some way of ranking them and understanding the categorization.
Martin Eve: So I invented a scale because there is no standardized scale for digital preservation
Martin Eve: where I gave gold medals to those that have 75% of their content digitally preserved in 3 or more recognized archives. Silver members in my scale are those with 50% of their content in 2 or more recognized archives, bronze 25% in one or more recognized archives and unclassified those that don't even meet the bronze categorization.
Martin Eve: So this is a scoring mechanism that works across 2 axes at the same time it works across a sense preserved, and in a number, and the number of archives that there are duplicate preservations in.
Martin Eve: So the very best in this would be to have all of your content in 3 or more of the recognized archives that I've been working with.
Martin Eve: whereas the worst would be, you have less than 25%, not even in one archive.
Martin Eve: So what does it look like overall? I looked at 7 million duis from our sampling framework, and I found some pretty disturbing results in some ways, but perhaps not unexpected to those who've been looking at this for a while.
Martin Eve: So those in the real danger zone, the unclassified space with that less than 25% in one archive, we found that approximately
Martin Eve: 33%. Third of all the content.
Martin Eve: From members that I looked at was in that group. Meanwhile, bronze, which you know is is okay, it's one archive with at least 25% in it made up
Martin Eve: approximately 57.7% of of the members that we we examined silver again. It's a much smaller percent, 8.4 6, and only about 2% or so made it into that gold category. The
Martin Eve: gold gold star system at the top there.
Martin Eve: So there's a worrying preservation picture emerging across crossraf members that we need to perhaps do something about.
Martin Eve: I want to know also which types of members were behaving in in what type of way?
Martin Eve: There's a variety of ways in which you can classify the size of cross-ref members, we can do it by revenue. So this is a chart that shows the breakdowns from those who have the very lowest levels of revenue at the top through to those that have the highest level at the bottom here.
Martin Eve: and I think what you can see is the silver bar, which is perhaps the
Martin Eve: a key sign that people are doing things well with at least 2 archives backing. The majority of their material increases substantially as we get down towards those with more resources.
Martin Eve: perhaps heartening, though even in though even among those with the lowest resources of our members, we do see that bronze bar where they are conducting at least one source of digital preservation, for for some of their material is happening. So there is an awareness growing Eve, among all types of publisher members that they should be doing digital preservation, and that it's something that does matter for their membership with Crossrath.
Martin Eve: You can also do this by number of member deposits. But I think the picture again is clear. You can see this silver bar grows substantially as we get down to the bigger members who are doing more deposits. The bronze bar likewise stays.
Martin Eve: kind of goes down again at the end, because the silver bars eaten it up, which is a good sign. But if you take bronze and silver collectively, as a marker of who's doing preservation apart from the very last bar of size, we've actually got a good good level of growth as we go down there. But clearly there are a number of smaller members here in this type of categorization who need us to to have a chat with them about what they're doing for digital preservation, because at the moment their material is not particularly safe.
Martin Eve: If you look at this on the works front. So that was looking at members as a whole rather than looking at the number of actual works, though. So we found that approximately 60% were preserved at least once. So 60% of the content in that sample had some kind of backup system in place that could rescue it if if the site went down.
Martin Eve: But that left approximately 30% in our sample that seemed unpreserved. And a serious risk with an exclusion of 14% for being too recent. So they're in the current year. So they weren't yet in digital preservation archives, not being journal articles or having insufficient date mess data for us to identify the source.
Martin Eve: So what are we gonna do about this? We've got a forthcoming peer review paper that sets out the the data behind this, and gives you the opportunity to read in more detail about the processes that we use to come to these conclusions. We've got some lay and easy read summaries of preservation situation coming out as well so that we can start spread the word even among non technical users, or less technically minded publishers.
Martin Eve: we'd like to conduct some direct member outreach. I think it's really important that we, in a non confrontational way, get in touch with people who are not yet doing this well and work with them because it benefits everybody to have a secure and persistent linking system between our articles
Martin Eve: and other types of work that use Dois.
Martin Eve: We're also working on experimental system called Project OP. Sit, which I've just started work on the last couple of weeks. This is a project that aims to integrate. Do I deposit with ingestion into digital preservation archives, and then tries to monitor an endpoint. So a doi resolution point to see whether it's gone down. And to tell people this is a problem. You can now view it at this archive instead, if you like.
Martin Eve: So if you Google for that project of Sit and Crossref, you should find the specification document and call for call for comment on that if you want to feed back on that it's not too late. Still, get in touch.
Martin Eve: And full charts and data set behind. These findings are available at the website there. The hyphen vaults fly. Dot dev.
Martin Eve: Thank you very much. I hope that was of interest.
Rachael Lammey: Excellent. Thank you. So I think there's
Rachael Lammey: already interested in going to zoom in on the
Rachael Lammey: the charts, and to be able to to find more information on that. So Rhiannon, do go and check I the link that Luis is just posted in the in the chat. And
Rachael Lammey: again, if if you've got, follow up questions.
Rachael Lammey: let Martin know.
Martin Eve: Thank you.
Rachael Lammey: And Martin, are you hanging around for sort of the next sort of 1520 min? So if you're mulling over a question, he'll still be. He'll still be here if you want to add answered, more more live? But yes, it's it's a really interesting analysis, and there's definitely follow up options that we can see both this cross ref on this and his community, I expect.
And there's a question just jump jumped into the into the QA. As well.
Martin Eve: I think that the this is because of bad mess data on locations. So the question was that there are cities, sometimes, or regions in the location or Co. What we call country. It's supposed to be a country feel. But sometimes people put more detailed information in there. So it's the best you know. I could spend a lot of time clearing up that data and going through. But with 7 million records filtering in just have to basically
Martin Eve: take it with a pinch of salt. The the location fields in there, and we've done our best on location.
Rachael Lammey: Oh.
Rachael Lammey: thank you?
Rachael Lammey: So the final presentation stroke demo for this session
Rachael Lammey: is duis for for static sites. So I should. Data from our from our
Rachael Lammey: Labs team is going to give us a quick demo, an overview of the static Site
Rachael Lammey: identifier generator using the Crossref website as a as a test case. I should appreciate a semi live demo of stuff that is in active development. But again, I think you've you've put some safeguard. You've you've put some safeguards in place as well. So I'll hand over to you to to talk us through it.
Esha Datta: Alright. Great! Thank you so much, Rachel. I'm gonna share my screen.
Esha Datta: Can everyone see my screen?
Rachael Lammey: Yeah, we can see the slide deck. Okay?
Esha Datta: Yeah. So I'm going to just kind of talk about this a little bit and then do a video demo because some of the processing takes a little time. And that's boring. So basically, I am going to give a demo of this lovely, wordy piece of software called static
Esha Datta: Page id generator. Because I couldn't think of a better name. It is developed to help create pids such as Dois for blogs or other research materials built by static site generators, such as Hugo Jekyll, or others. Currently, the software is being tested with Hugo. We decided to develop the software because increasingly at Crossref, we are seeing a need to develop permanent urls for our own use on our website
Esha Datta: and could see a use for the wider community as well. Our website is built using Hugo the software
Esha Datta: can track a git repository of the static site in question. And if a user specifies a path, it'll start focusing on any files under that path. It'll generate unique ids for the files that a user wants tracked. And if the user is a cross ref member, it'll build the Xml deposit files, deposits the metadata for the files into cross Ref registers the dois and adds the doi back to the file in question.
Esha Datta: If you're not a crossword member for now, basically, all it'll do is features one and 2, which is, tracks the files and generates a unique Id, but we are developing a Plugin architecture so that it can accommodate other use cases and other registration agencies, and also other types of unique ids that you'd want. So I'm gonna start with the end result of this, which is
Esha Datta: that here is an example page of the test version of Crossref
Esha Datta: of the Crossroft site. So I basically just created this very lovely test page and ran the script
Esha Datta: against it, which then deposited this this metadata into crossref, which you can see in the Api. And here's the doi for that, and it can also then be used in downstream applications set up, such as the metadata Search, where, if you did a search on this, you would find the same
Esha Datta: article. And if I go back to it, here is the file.
Esha Datta: So basically, I'm going to show you how to show you 2 ways of how I use the script. First is in the Get Lab Repository, which contains the test version of the site
Esha Datta: and then the second is the command line version. So in this repository we run the script using Git lab's continuous integration setup. And if you use, if you have a repository that's in Github. It has a similar process. So I first ran in the Git lab Repository, a setup process that creates a config file which contains the information. Let me.
Esha Datta: I have it queued up in my video. So here's the config file. So here, you see that I'm asking the script to track everything in the repo. I've put in a test. Do I prefix? I have this crazy, long domain, which is basically just the test version of the sites domain.
Esha Datta: I'm specifying that I want an Id type of doi. And the Json file basically contains all of the information of the files that are being tracked.
Esha Datta: And now I'm going to play the video, not sure how much time we have. So I'll check in again after I've finished the get the repository part of the demo. And if we have more time, I can also show you the cli.
Esha Datta: Yeah, I think we're okay for time. Okay, cool.
Esha Datta: A Json file contains. Can you all hear that all of the information for the file
Esha Datta: start tracking a file? I created this file, which is new and basically added some front matter. So it includes some of some basically labels that is recognized by the Hugo site.
Esha Datta: And also crucially, I added this X version tag, which basically tells the script to start tracking it. The value to the right of X version is in semantic version, style. So basically, the first 0 tells you that this is the major version. The next one is the minor version, and this is the patch.
Esha Datta: So the script looks for a default version of 0 point 0 point 0, and it knows that this is a new file, and to begin tracking it. So once I push this file. I start to get a process that runs this job and it pulls down a docker image and
Esha Datta: runs the script essentially. So we are mentioning giving some credentials for it. And then we are also saying that it needs to check the repository over here, that submission type is cross Ref.
Esha Datta: and that it needs some more submission, information, or deposit information for the script to deposit the metadata that you will be using eventually. So what it does is it adds the file information to the Json file. It deposits the Xml. And then it also
Esha Datta: creates a doi and adds it back to this file, and you know that all is well because the job has succeeded. It has run successfully. We can check the page back again, and we can see that a doi has been added to this page.
Esha Datta: and we can also see that once the site has been deployed to production. If we click on this and go to this dui, it takes you to the site.
Esha Datta: to the page that's been deployed to production. So this is basically how you would run it. and continuous integration on a git lab hosted repository. There is a similar operation that you would do if it was hosted on Github as well, because Github also has a continuous integration setup
Esha Datta: or running the script on the command line. I have cloned the static page id script generator on to my computer. And I have installed all of the requirements in a virtual environment. And in another
Esha Datta: terminal I have my static site Repository. I first need to initialize the repository for the script which generates 2 files that helps the script track. The versioned files so to run the initialize script.
Esha Datta: I run this command, which requires a few arguments that tells the script a few things. It tells the script that you to track this particular repository
Esha Datta: to track the path in the repository which is content. It gives it the production domain that it needs to generate a doi and a doi prefix.
Esha Datta: So once that is generated it will create 2 files. This is to track the files, and this is essentially contains all the values needed to generate Dois. So I already ran this, and so there is a config dot yaml and a pid, dot Json, which looks
Esha Datta: like this for the config. Yeah, Yaml file, and it's just an empty pit, Dot Json file, because I haven't run anything.
Esha Datta: So in order to let the script know that I want it to be tracked, I add this particular tag with its value in the front matter. So I tell the script that I want this to be versioned, and I add an exp version tag to it. And I follow the semantic versioning
Esha Datta: style, which is major major version, minor version and patch version. So currently, we have functionality that looks to see if the version number is 0 dot 0, and it's
Esha Datta: belonging to this tag, and then it will start to run all that's needed run the script after telling the script which files we want to be tagged.
Esha Datta: and we do this by again specifying the repository path. We're telling it that the submission type is going to be crossref because you're going to deposit this into crossref. And then we have another file that tells the submission scripts, some more information to make the submissions successful.
Esha Datta: So it's going to generate some
Esha Datta: hits. It's gonna track the files.
Esha Datta: And it has now submitted the file. And now it's going to check the doi registration status.
Esha Datta: Once it runs it, it checks the dois, and then it adds the doi back to the file which you can see
Esha Datta: over here.
Esha Datta: So now we know that this file has a doi and can be accessed once this once the website has been deployed to production.
Esha Datta: So that's how you would run it in the Cli so wanted to show you what it would look like if I
Esha Datta: checked the doi from the command line. So this is a page that has actually been deployed to production, which is the test
Esha Datta: website that I have. So if I
Esha Datta: copy and pay to paste this, or just follow the link, this will show me the page that has been deployed, and, as you can see, the doi is listed on the page here. And this is all of my test text, of course.
Esha Datta: So that's basically the demo for this. Thank you for bearing with the video and the extraneous sounds. Future steps include that. It's still an active development, and we still have
Esha Datta: a ways to go, including incorporating it into the crossroads website, workflow. I'm I'm planning on converting this into a library and allowing plugin functionality so that it can accommodate other types of used cases as well, and I'm happy to hear more feedback from all of you. And you know, see how we can collaborate better on this. Thank you so much.
Rachael Lammey: That's great. Thank you very much. It all worked very very smoothly, and there are a couple of hopefully quick questions. In the QA. If you want to call those up
Esha Datta: or I can. Just
Esha Datta: yeah. Is it the do you have thoughts? Is that the one? Yeah, the thoughts of like the
Rachael Lammey: on the archiving of the final rendered static page with images, for example.
Esha Datta: that's a really good question. I haven't really thought about it. But
Esha Datta: yeah, that is, that is super interesting. And also, yeah, we could also talk to Martin Eve about possibly looking into how to preserve this. And so that's a that's a nice tie in into that for sure.
Rachael Lammey: And and then there's a second question about or actually, Martin, I'll let you jump. I've seen you've unmuted. Let's let's take a bit more time on that question.
Martin Eve: I was just gonna
Martin Eve: draw attention actually to Martin Fenner's work that was mentioned earlier today, I think, in a different session. This been looking into the preservation of logs and static sites. So there's already some experimentation around the preservation function here. But you're right. We've we've got an ideal point. Now, if we're signing up a dui to these items to think about how we might get them into an archive, so that we know that the stuff is preserved at that point.
Martin Eve: because obviously, the
Martin Eve: if. If we just open the floodgates and say everyone can have a dui for this content. But then, unaware that there's that preservation responsibility, then we're in quite a difficult position.
Rachael Lammey: And then there's another question. Aisha,
Rachael Lammey: how does this tool handle? Multiple resolution?
Esha Datta: Yeah, again, a very good question. Currently, it's still very much an active development. So we should definitely talk more about all of those types of use cases.
Rachael Lammey: Great. I will give people a few more minutes. I
Rachael Lammey: the next session will start on the R, and I'll give people a few more minutes in case there are any final questions. But I don't miss wanna miss the opportunity to say, thanks to all of our fantastic presenters, and also for for your really good questions. I hope this gives a flavor of the
Rachael Lammey: the variety and even just a small subset of the things that we're working about and thinking up about across the various teams.
Rachael Lammey: Brace has just posted the link to the next session, which is a discussion among crossrest staff and other members of our community on what we still need to build a research nexus. So I hope we hope that you'll that you'll also join us for that.
Rachael Lammey: Yeah, if you want to take a few minutes.
Rachael Lammey: ask any further questions, or go and get a cup of tea, coffee, glass of water? This is your chance. But thank you again.
Rachael Lammey: Okay, I can see people starting to
Rachael Lammey: starting to to head off and take up the opportunity of a
Rachael Lammey: of a coffee again. There are lots of mechanisms by which you can, you know, by which you can get in touch with crossraf our community forums. A great resource for that as well. So this isn't kind of the end of the opportunity to to ask questions and and to find out more information. And obviously we'll we'll follow up by posting the video and a link to the
Rachael Lammey: the slides in the in the coming days. Once we've pulled everything together. So I'm going to leave it there. Thanks again, and we hope to see you in the next session.