Communicating your COUNTER Compliance and other essential information
Communicating your COUNTER Compliance and other essential information
https://asa1cadmoremedia.blob.core.windows.net/asset-3e1e37ec-91d9-4232-aead-3fd4341c5c5e/Communicating your COUNTER Complaince and other essential in.mp4
Hi, everybody, just giving everybody just giving another minute to allow people to come in.
OK, well, welcome everybody. I'm Lorraine Estelle, I'm the Project Director at COUNTER and really grateful to all of you for sparing the time to come and join us this afternoon. You won't be hearing very much from me, but you will be hearing from some experts. And first up, we have Joe Lambert and Laura Wong, and they both work for JUSP the Journals Usage Statistics Portal.
And I'm sure you're all familiar with that on this call. So I don't need to say too much about it, but I will just say that Jo Lambert, in addition to her role at just, is a member of the COUNTER Board of Directors, which is, I think here in both those capacities today and where we've heard from Laura and Jo, I'm going to hand over to Bedřich Košata, who is going to take us through new COUNTER registry, Bedřich works for Big Dig Data who have done a fantastic job in building this Registry for us.
So Jo and Laura, if you are already, I'm going to hand over and over to you. Excellent, thank you. Lorraine, so I'm going to start off, would you mind just moving on to the first slide? Hopefully you can hear me. Yeah, brilliant. OK, so this is the agenda for the session today where I'm going to start by talking about the importance and the value and the benefits of the COUNTER registry to both publishers and libraries.
And then Laura is going talk a little bit about how the COUNTER registry is used by initiatives and products and projects like JUSP others, and then we'll have a demo, a Q&A and next steps. So the Lorraine, would you mind moving along? Perfect thank you. So the COUNTER registry is a really important tool that aims to provide a single point of access to information about compliant publishers, platforms and hosts.
So it details information about the different COUNTER Reports that are supplied by each of the providers, contact information and SUSHI implementation details. And then, with the recent development of the COUNTER Registry there's now an area that you can use to communicate information about data issues, restatements or any other information that you want to note and communicate to people. So if we can just move on to the next slide, it's a little bit of background information.
So would you mind just muting if you're not speaking at the moment? Thank you. OK, so I'll just talk a little bit about the value of the COUNTER registry. So it really offers a number of different benefits to you and to your customers. I think really, if you're investing in achieving compliance with the Code of Practice, then the Registry really enables you to demonstrate the commitment that you've indicated towards providing standardized data.
But would you mind moving back a slide, please? Right? and. Do you mind moving back to the previous brilliant, thank you. So we know that libraries really value access to COUNTER statistics, and the Registry really helps to communicate that indicate your commitment in doing this. And clearly, once you've put a lot of work into developing the road to developing COUNTER compliance and achieving compliance, then you'll really want to shout about that to your customers.
So the Registry offers this opportunity to indicate who's compliant and really service an indication of quality. So making sure that you are represented on that registry really sends a message that you've achieved certain quality standards. You'll want to make sure that your customers know which reports they can access and how they can access those. So recordings see information in a single place really helps to reduce support requests for information.
And so this is going to be useful really for your customers who are wanting to gather this information and those who are external to the organization. But it's a really useful resource, actually on an internal basis. So particularly if maybe you're based within a larger organization where you might have staff that lack the awareness or the knowledge of COUNTER and SUSHI, and it's a useful place to be able to point them to.
But as I indicated earlier than the Registry also provides this important role, enabling you to communicate data issues or restatement, so you might currently use things like mailing lists or other tools to do this, but sometimes messages can get missed. We all know, we all know the problems around the email, so having a single place such as the registry to communicate those issues and more importantly, when you've got to the point of resolving those issues, I think is a really useful thing, and it's obviously making things much more efficient.
Something that Lorraine flagged actually when we were talking earlier prior to this webinar is that apparently an increasing number of you are starting to provide item reports that might be available but not yet audited. So the notifications area is a really good place to highlight any work that you're doing in that area. All your library customers who are maybe wanting to harvest statistics into local systems.
And things like their library management system or a stats application, then the registry provides real efficiencies. It's essentially avoiding them, having to visit multiple websites and places to gather this information. And so they can be certain this information is being managed and updated by you as necessary and that they're looking at this comprehensive and up to date record.
I think understanding the point at which data issues were identified and subsequently resolved is really valuable for your customers. And so this can help them with things like retrospective analysis or reporting enables you really to be transparent and record any issues. So you'll know that if, for instance, your customers pulled reports at a particular point in time and maybe save them locally and then they need to rerun a usage report, if they noticed discrepancies, then that log of information will help them to identify what happened and when do they understand what's occurred?
And again, I think that this is really helping to cut down on support requests to potentially your help desk and your teams. And then we have intermediary products and services like just the CC-Plus initiative, and they really depend on this Registry for a single point of information. And Laura is going to speak of this in a little bit more detail about how the COUNTER registry is used by JUSP.
But before that, I just want to cover a couple of quotes. So if you can move on, please lane to the next slide. So representing a library consortium and also the CC- Plus initiative, Jill Morris from policy provided this particular quote. So here she talks about the Registry as an advocacy tool for COUNTER compliance and for offering an accurate record of key details. And Jill outlines how libraries and consortia use the Registry to assess the extent to which publishers and content providers are meeting library needs.
And she also highlights its value in really helping to exploit access to the data and the stats. You've obviously spent a lot of time and resources in creating. Do you mind moving on to the next slide, please? Great OK, so this quote from Irene Barbers representing library perspective really reiterates these efficiencies offered by the registry, both from a library and a supplier perspective.
And Irene highlights the importance of this single point of access to information about reports, and she access details. So using the Registry to prepare and support search requests, rather than having to interact with multiple websites and and again reducing the support request to your help desk. And then the final quote, please. Thank you.
So finally, this is a quote from Peter Simon from Newsbank and outlines the value of having admin access to manage their Registry entry and keeping this information up to date so they have that information available and easy to access that. So I'm going to hand over to Laura now to talk about the specific instances where just is using this to manage information, so. Laura, thank you.
Thanks Thank you. Thank you, Lorraine. OK, so before I go and talk about how we use the Registry, I just wanted to quickly go over background to just to give you a bit of context and particularly those who may not be familiar with the service. So it stands the Journal Usage Statistics Portal. But we actually cover a lot more than that. We cover books, databases and platforms, and we're also going to be looking at including item reports in future.
And I come back to that a bit later. And so basically what we do is we collect counter reports on behalf of over 300 institutions on a regular monthly basis from around 100 different platforms. So we collect a lot of COUNTER Reports. So we're very used to working with them and the only collect and the reports via SUSHI because we're working at that kind of scale. SUSHI is incredibly important for us.
Without it, it would. We just wouldn't exist. We wouldn't be able to be manually harvesting reports and loading them. We really rely on that automated process and we rely on it running smoothly and knowing when there are issues and getting those resolved. Another thing to note is we only collect last reports, so this enable us to collect the full set of data on behalf of an institution, and then we provide access to that data through a range of reports and visualizations through our interface.
And the key thing about it just is that it saves libraries of time and effort of having to go to multiple websites to collect that, but that data to log in, to hunt around to download the reports and aggregated together because we do that for them. And the same sort of applies to the Registry. One of the key benefits of it is that time saving and effort. It means we don't have to go to multiple different publisher websites to find this information.
We just have a single source that we can go to. OK, so now I'm just going to run through some of the main use cases of how we might, how we use the Registry in JUSP, how we hope to use it more in future. But this will equally apply to any institution or large group of institutions that may be wanting to harvest and data at scale. Next slide, please. So the first situation for us when we use the registry is when a library asks us to add a publisher or supplier to just so the very first thing we want to know about this, this publisher is are they council compliant?
Are they providing counterpoint reports? And if so, which ones? And having access to the registry means that we can ease quickly and easily. Look up this information without having to say go hunting around publishers websites. And in some cases, this information isn't actually available publicly. Sometimes it would be behind a login.
So, for example, information about COUNTER compliance or the reports available are available to customers only. But as we're not a customer, we can't. We can't see that. So having that information easily available was invaluable. And this really helps to inform the conversation. The approach we have with the publisher, if we know they are COUNTER compliant, what reports they are offering, it can open up the conversation we can and we can give them guidance on what's required and to get them to participate if they're not COUNTER-compliant.
And that changes the conversation and we would encourage them to become so. OK next slide, please. The next situation where we refer to the Registry is when a publisher actually joins JUSP so just sort of beginning to collect the data. Now, often the first point of contact we have with the publisher is with a sales representative, and they're generally not that familiar with SUSHI or data collection or usage data.
So it can really help for us if we have somewhere to go. We can find out who the usage Data Hosts that publisher is working with, so we can instantly get an idea of what's going to be involved because we're used to working across multiple platforms. Some of the key data that's providers we're regularly working with already. Similarly, it's useful to know how to go about getting credentials, so credentials for individual institutions obviously need to remain secure.
But the process for actually how do you get to those credentials is really useful to know. And together, this just overall just seems like the kinds of processes we can provide guidance to the publisher about what's required and make recommendations based on what we have been optimal processes in the past. So in the case of just we've tried to work with the publisher of the to aggregate credentials together to reduce the burden on the institution, but there are some cases where we would want to go directly to the institution to asked them to send us credentials.
And of course, our other consortia or other organizations might take a different approach. So in this case, it's really helpful, as I say, for that, having some more we can point institutions to. So this is where you go to get your SUSHI credentials because often they aren't familiar with working with SUSHI either, and they have to sort of navigate around various admin sites to find that information.
So I say just having that, those instructions on the page are really useful. OK next slide, please. So another case where we will make use of the COUNTER registry, we have done it with the previous Registry is when we are looking to expand the coverage of the reports that we offer. So this could be where we're just looking for gaps.
So often we have a publisher signed up many years ago. They may change the reports that they offer. They may add new platforms and just being able to do that sort of systematic check across the board of what data we hold and what data is on offer and just identify where there's any mismatch can really help us fill in gaps and ensure that our users have the fullest data possible. Another situation where we would use it is to say we're looking to add additional reports, so we are going to be looking into including the Master Report, and it's good to hear that more publishers and suppliers are going to be providing this going forward.
So we're looking to include the Item Master Report, and it would be a really big task for us to go to every single one, every single supplier and publisher and find out whether they're offering this report. So having a central place where we can go to and get that information, as I say, it's really valuable when it allows us to assess, assess the availability of the reports.
The scale of work that's involved for us. The value of adding additional reports in planning the time scale. So it really helps with our planning and management. OK next slide, please. It's two more. OK, so the next example where we want to refer to make more use of the COUNTER registry, in fact, is around harvesting issues.
So generally speaking, we collect data on a monthly basis and it's all works very smoothly and there are no issues. But every now and again, things do crop up. So it could be that there's been a change at the publisher side, change of platform, change of social set up. We haven't been notified about or it could just be a temporary problem. And in this case, it's just useful for us to have someone to go to where we can find out whether we need to take any action or whether it's just a case of bite again and try again later.
And if we need to take action, then having a publisher contact knowing who to contacts for really helpful here. Because again, sometimes we may have set up the SUSHI harvesting many years ago with a particular contact, they've now moved on. We now need to get in contact with someone at the publisher. And we're not sure who the best person to speak to is. And so all of this really helps us resolve issues quickly and reduces gaps in the data.
So we're not having large amounts of data for our end users. And as Joe mentioned earlier, just having that single point of reference where we can check for updates on issues and also be able to point our users to is handy so that we can point everyone to the same information. We don't have different information all over the place. OK, my final slide, please.
So, another situation that sometimes occurs is that there are corrections or changes or misstatements to the stats. Sometimes we're informed about this directly through for a publisher context. More often we just find out accidentally when someone queries a discrepancy. And this could be months after the change has taken place.
So what we'd like to do is find out what the issue was. And so we can respond and inform our users of why that change has happened. How long and how long it's been affected and whether it's been resolved. Because once we know what the issue's been resolved and how long the affected period was, we can then go back and re harvest that data. And so having access to timely information really ensures that we ensure that libraries have up to date stats and what we're holding is the most, most up to date for them.
And again, just having that central point of reference is really handy for keeping users informed about progress as things develop. OK that's everything I wanted to cover. Is that a better way to? How will everybody know I will be showing interest in the real world, but what the registry looks like and how you can use it to edit your information and update it so that the librarians and other users really see what the most up to date information.
So I will share my screen. I have prepared. Like two very short slides, just about the terminology that was already used here, but I would like to make it clear so in the Registry we use like two terms, Platform and Usage Data Host and the difference between them is that the Platform is where the actual users or readers go to read data, they download their articles and then ebooks and when they browse the databases.
But it doesn't necessarily have to be the place where the data about their usage is stored. Some of the platforms, some of you do this in-house, but some of you outsource it to someone else, to someone who we call Usage Data Host. And this is a service which is storing these user usage data and then providing the sushi interface to the outside world. And because there are different setups, some of you have in-house, some of you outsource it.
We split these two roles in the registry and we will see later on what each of these users is able to do and not to do. So one of the important things here is that a Platform, as I said, may host the data itself but may use some external Data Host but also a Platform may use different Data Hosts for different versions of content.
This is something that we have seen, often with the introduction of COUNTER 5 that platforms that have had for data like in-house then outsource the countrified to some external Data Hosts. But the Registry is, of course, capable of capturing also other possibilities. And before I show you the Registry itself, I will just show the next slide.
And this is just to make sure to cover upfront what is and isn't possible when it comes to user roles or access levels. So if you are a Platform manager so you are assigned a Platform that you manage, you can basically change all the data about the platform. You can also change the SUSHI details, and you can also add a new notifications about possible issues or data objects.
On the other hand, if you are a usage data host so you are a host for hosting data for some of the platforms. You can only edit the data for the Usage Data Hosts that are there, which is very limited, but you are not allowed by default to edit anything related to the Platforms you are hosting. This is simply because they are different setups, and we do not want to allow someone to edit the data, even though, let's say the Platform manager would not be happy with that.
So this is how it is done. But of course, it is possible to be assigned different to different roles so that you as a usage data host manager, maybe also assigned the role of platform manager of all or only some of the platforms that you are that they are hosted on your server. So in this way, we can make it feel like flexible depending on the setup that you are using. And one more small comment is that most of the changes that you will be doing in the registry are not like immediately shown at the COUNTER registry itself, but they have to be approved by the COUNTER staff.
So even though you added something, please don't be worried when it doesn't show up immediately in the COUNTER registry. It has to be. It has to be checked and approved by the COUNTER staff. The only exception is the contact information, which you provide, like our emails and so on, because this is the reason we expect you to know what you are doing and to know it better than the counter staff that would be checking.
So this is what the two slides. Now I just switch to the actual. Registry at first, I will show you the I say, the public interface of the Registry, the Registry itself is very simple. It's just a few pages and it is it was made so that it's really very straightforward for the users to use it. So if you come to the Registry, this is the first that you see and this is just a list of all the platforms that are listed in the Registry.
You can see their names some abbreviations when they are used. You can see who is the content provider. You can see the Host Type, which is something that is specified by the COUNTER Code of Practice 5. And you can also see a link to the website and information which SUSHI is active and also which reports are active for that Platform. It is possible to search here if I was looking for because I would be able to find it very quickly and then I can go to the.
The detail of that particular platform here, you can see the information, some basic information about the platform itself with some contact information here. This contact information is really related to the platform itself, and it might differ from the contacts that are. Then given to specific COUNTER releases, so if you have different, different people managing COUNTER 5 and COUNTER 4 releases and so on, the contact information may be different.
Oh, so this is the basic information here you can see, like information about the current releases, which right now is under fire, so you see the COUNTER 5information you see when was the last audit? You see all the supported reports and you see a contact that is specific to this. COUNTER 5 release, which in this case is the same as for the platform itself.
And then you see some SUSHI information. I'm sorry. This is something that is. Like, we are going into details about the SUSHI service. Like the SUSHI server you are. And some other specific information, like if the customer if the request or ID is required. If the API is required and even some information, then you can obtain it, or if it's like, what's up?
Maybe something something about the format of the ID and so on. And then here this is why I chose the greater is that they already provided some user notifications, which is another very important part of the registry. And this is where you can let your users know that there has been something with something wrong with it or some issue. And what is the current status?
So you can see like two different messages. One of them was in October, and this was marked as a generic message. And it says that there has been some trouble with recording PDF downloads for this time period and that it will be resolved in the future. And then there is another notification this issue, which is related to it. And this says that this has a type of data harvest, which means that the action to take when you receive this notification should be to harvest the data for the affected period.
And it says, OK, we have resolved the issue with the PDF downloads, and you can now download the new data and then you face data. So this is really very important, especially because the new registry has an end and API. In fact, this whole new website is using this API in the background to receive the data, and this API can be then used.
By statistics, software and so on to automatically harvest the data based on these notifications without the user needing to do it manually. So you can also see that we have some inactive releases here. This is the kind of form you can again see which reports are supported by income support for this platform. But there is no SUHI service defined for this COUNTER version.
So we don't see any specific information here. So this is the most important part of the COUNTER registry. Then there is the list of all the notifications which are like you take across platform, so you can see. You can check it regularly for news here. If some of the platforms that you use has released some notifications and there is a list of their usage details which simply shows like all the details and how many platforms they host, and then you can into detail.
You see details about the Usage Data Host and also which platforms are hosted there. And some information about the audits. So here you can see that there is a finished and already way accepted by COUNTER. It and now there is an ongoing audit. This second one. So this is what the general public sees.
And then if you use this item here, you do it. You can get through to the backstage. Well, I would be showing not the backstage of the actual Registry, but the local copy of it, because if we make some changes, I would like not to like. Break anything on the public website, so the changes I will be making are only locally on my machine.
So I am here locked in as a platform administrator, but also as a usage data host administrator, so I have to do roles. One of them is that I can manage platforms and I can see that I can manage six platforms if I go here, I can see which platforms. These are. This is just this. I have assigned these just randomly to my account, simply so for this, for the purpose of this.
All of this. Presentation it doesn't reflect any real, real use case of something. And I also have assigned the role of manager of Atypon Usage Data Host. Again, this was just for this presentation. So I will show you now how you can use the COUNTER registry to manage your data.
And the most important thing is here and the platforms you can choose the platform you want to manage. And then you will be shown mostly the same information that is available in the public interface of the registry, so you can see here some of the basic information information about it. And then you can see the contact information, this contact information is the part that you can edit on your own.
So this is not something that is. It has to be approved by COUNTER. On the other hand, if you decided to change these more official things than you will, it will be approved by COUNTER. So I will try just to test it now. I will change the whole style and maybe either delete some of the something from the address just so that we can see how it works.
And you can now see that the information here is still the same. That you can now see that there is a proposed change and this is the change of the host type and address. So this way you will see that this is something that is still not approved, but you have made this proposal and the counter staff or someone else will see in their system that there is this change and they will be able to review it and then either approve it or reject it, depending on what they think.
But if they reject it, they obviously probably contact you and tell you why they did it and so on. But while it is in this state, you can still edit it. So you can make more changes, or you can just discard the proposal if you decide not to make the change. You can just discard it and then it will disappear from the system. The contact information here, there is an interesting thing about it, you can change it freely, but it is done in a slightly roundabout way, so it's not you will not be directly anything that the contact, even though you can using this button.
But we made it so that the contacts may be shared between different, different platforms, let's say, and so on. So this is for the case where, for instance, there are like 20 platforms which are hosted on the same usage data house, and you would like to use the same contact information for all of them. Then it doesn't make sense to fill it.
Been for all of them, and then when it changes, change it again on implemented in 20 cases. But you will simply assign one of these contacts and then when you change that contact, it will change for all in all of the places where it is used. So this should make the data there more consistent and make it simpler to make which edits of the content.
It's pretty straightforward. Here you can see. The list of supported reports COUNTER 4 and 5. I have already made some changes here. These are like if you have a look at the COUNTER 5, you can see that these are either with this checkmark or with the cross, which means that the ones with the cross are not. used at all.
And this is the checkmark are the ones which are supported. But here in the country for case, you can see some with this, it is up up pointing arrow, which means that these have been proposed. But to be activated for this, for this social service, but are not there. You can also there is some information here. And this is again the case where the counter staff has to review this data that you have edited.
So I have already edited here and I can maybe say that, OK, I don't want this. We are to be present there, but I want BR4 to be activated, and now I also want to activate the air for COUNTER 5. And now if I put it to make changes, we will see that there are these new BR3 and BR5, are proposed to be activated and also the BR4 is proposed to be activated.
And now Lorraine, or someone else from the COUNTER will see that there is this proposal. And if they approve it, it will turn again into these. These these, these ones will turn into these red ones and it will be immediately visible in the registry until then in the COUNTER Registry. The Registry still shows the old. set up. And now we get to SUSHI services, which is where the platform actually gets somehow connected with the usage data, so you can see that we already have this SUSHI service defined for COUNTER 5
You can see that there is some contact information here again, because this information may be something that is not it might not be the same as that is given here for the platform itself. It might be something that is really like technical and really related only to COUNTER 5 SUSHI. In fact, I would recommend if you have some more technical contact than specifying them here for the SUSHI service so that you can in this way point the users in the right direction.
If they have some SUSHI related questions, they can go directly to the technical support. Rather than going here and there, you would have to re-route them to the technical staff. Again, but of course, you can use the same contact here as you have used before on for the whole platform. And here again, you see all the information about the SUSHI service that we have seen that we have seen here.
But you can edit it here. And you will see like the. For for each of these. Each of this checkmark, here you can see also there is also a checkmark here. The API is required if there are some, if the platform attribute is required and so on.
And then this information here, this is like this is some kind of extra information related to this checkbox. So in case you, for instance, say that the API key is required and you would like to save it, then it will tell you that there is a problem that you have to provide this additional information. So if you say API key is required, you have to give the user some kind of information about how to obtain the API key.
If it is available in the admin interface, or if he should write them an email or. So let's just put something here so that we can save it. And now if I save it again, see? That there is some proposal for change, I can still edit it or discarded or wait for, for or 8 to approve it. If I want to add another SUSHI service, like for COUNTER 4, I will use this add SUSHI service button.
I can again say. select where I am hosting my data I can use all these Data Hosts that are available here, and I can only select different COUNTER release that from the one that I already have. So if I already have COUNTER 5 created, I can only select COUNTER 4. I will be like providing the URL here and so on. And once I say with.
It it will create another SUSHI service there, but not right now I am missing some. Someday OK, so right now, now here is this COUNTER 4, but this is not the objective. It has to be approved again. So this is how you hope you will be editing. Editing your information, it may maybe look a little bit like.
Complicated because different data are edited in different places, but the way we've structured it is to make it possible to be really flexible with it so you can have different COUNTER versions or on different details, and so on. And if you decide to change the data out, you don't have to change the reports which are supported. You just don't change these data here. And so this was about the platform management.
If I go back, there is the usage data management. I also use this Data Manager. It looks very similar, but I only have the possibility to change the basic information about these data and contact information. And I also see some information about audits, so there is not that much to change here, and this is mostly data that is not interesting to the librarians because they should they will probably be interested in the contacts and so on, which are really great, which are saved with the platform.
And here are the notifications, which is. Always available to if you are a platform manager. And here you can manage the notifications, there are no notifications right now, but you can add some. Here is some information about for what. In which case you should use this service and when not to use it. So it is not intended for the regular information like another month has been released.
And so on. It is more for the cases where there is some problem with your data and you are working on it. You would like to let the users know or when you fixed some data and you want users to re harvest. The notification is always a sushi service specific, so you are not only using the platform for which this is used, but also the sushi service, because the issues are usually only specific to one country release.
So if it's COUNTER 5 specific, it doesn't probably relate to COUNTER 4. So if I choose one of the services here, I will put some subject. It doesn't matter. It's just like in an email subject, and here I can choose between two different types. If it's like a generic message, I just want people say that there is a problem.
Tell people that there is a problem, or I can use this data, which means some data has been updated and you should re harvest. Then what is who is the source of this information? And in this case, I can only choose the content provider. It's also possible that this source could be like the COUNTER organization itself, but I cannot choose it here if I am not like the administrator.
And if it's related to data edit or but even in other cases, but mostly in case of data edits, it is very useful to add some kind of information of what time period was affected by this problem. So if I know that for 6 September till the end of the year, some data was not correct. And I want people to harvest. I can specify the dates here.
So that people know what data range is to do a harvest, then I can write some message here and I can if it's also about something about data, I can also select which reports were affected. So if I know that it was only the DR Report, but not the TR Reports and others, they can just report. And once I'm ready, I will submit it, and it's now I will see what is.
I like the overview of what I have written. Here is the title, and here are the other information and but I have the way I have done it now. It's not hasn't been released to the public yet, but I have to do now. If I want people to see it, I have to click this publish button. But what is important is that once I do it, I cannot change it, I cannot go, cannot edit it.
This is simply to be able to have the trail or of what happened happened consistent. We don't want to show people some message that they have to do something and then change it retrospectively after one month or something because we never know when people will read it. So we really want to preserve the history. So once you release it to the public, you cannot change it. You can release another notification that will be updating the previous one.
But you cannot change it unless you contact Lorraine or the counter staff and ask them to change it. They can do it, but you, as a platform manager, cannot do it. So this is the time when you should be reviewing the. So the notification and once we are really like. Sure, that this is what you want to release, then you do publish again, ask you if you really want to publish. And if you do so, then it's published and you cannot change it anymore.
You are just seen here as a published notification. But you cannot edit it anymore. So this is like everything that you can do in the cancer registry. And before I will switch to Lorraine and therefore we will have questions. I would also like to point out that as I mentioned, there is this API that is running in the background in the Registry, and this can be verified by anybody to get person like.
For so long, the machines can communicate with each other and get the relevant data. And I have been just now working on integrating the County registry into our product, which is called selous, which is for usage statistics. I would just like to show you quickly how it could be used there. So that you have some idea of what the benefit would be for the user.
So if you are now adding new credentials here, some of the platforms I only mark three years, they'll be they'll have this Registry. Then here, which means that we already have connected them with Registry. And if I again choose the De Gruyter as an example, if you select this spot for the legal, download the data using the API from registry and it'll show you the URL of the SUSHI server, we will tell you some information about the Customer ID so you will see whom to contact to get this information.
You will see the same information for the API key. You will see that the Requester ID is now disabled because it was marked as not being required in the Registry, so the user doesn't have to bother with it. And if you want to select which report sites you would like to harvest, you will see this blue checkmark there for all the platforms, all the reports that are marked as supported in the COUNTER registry. So this makes it really, really much simpler for the user to understand what he needs to do, where to obtain this information and so on.
And also it helps them to pre-fill some data that he would otherwise have to find on his own. So it's really something that we are looking forward to seeing, like filled with data because the more and more data there is in the Registry and the better the quality, the easier the life will be for our, our customers and also your customers. So we are really looking forward to that, and I would be very happy to see the Registry as full of data as possible.
So this is everything for me. Thank you very much. I'm ready for questions. So can I just ask, are there any questions you either want to type them in the chat or if you want to unmute yourself?
Are there any questions in terms of any of the points that we've presented any of the demo that you've seen? Hopefully, it's all self-explanatory and you'll go away and populate the Registry. And I think, to reiterate, is a very useful information resource for everybody, so we would just like to see it populated.
And as full as possible, so hopefully we've sort of outlined fairly in the benefits of doing that for all parties. Yeah, I was just not wanting to pick on people, but we have got a few people here who have used it even put down. So I can see. Stuart, for example, is on this call. And I just wondered if, if you'd like to share with us, your experience of inputting the data.
Yeah hi, Lorraine, Thanks very much. It's been very simple, actually. Once we have our admin, we represent about 26 Platforms Sorry, sorry, we can't quite hear you, ok? Apologies there. Give me a minute, I'll just change my microphone over.
So it was my fault I put Stuart on the spot there, he wasn't expecting it. Is that better for you? Yes, it is. Thank you. Sorry OK, good. Good yes, it's been. It's been very simple for us to do so. We just log in as an admin representing about 26 different publishers.
And then just to sort of check, the reports there are sushi credentials that we have for all the publishers are the same work on the same basis. So yeah, from our point of view, it's great to update it. We're just encouraging to get the correct contact details that the publishers want to have listed, et cetera. Updated as well. But yeah, from overall, we hope that it's going to be well-received by the librarians to make use of it.
Thanks to that. And any other questions or comments? No, well, one other thing I would just say, I know some of you on the call already have your account set up and you can post your SUSHI details and your changes if you haven't already got an account set up, please just email me and I remind you about that in an email.
later on. We'll set up your account and then you can go in and make the changes that you need to make. One other thing I would just point out is when you get the invitation to activate your account. If you don't activate it, it expires after a while. So I would encourage you, once you get the invitation, please activate it so it doesn't disappear.
Super Jo, anything to add from Laura from the JUSP perspective. No, I don't think so right now, we just encourage people to register their entry. Beda, any last words you? Last word. It sounds very ominous that I won't last forever.
I didn't mean that. I have currently three COVID positive people in my family right now in the same flat, so asking me for the last word. Oh, but they are OK. It's like, OK, OK, I just see that we just got a few questions in the chat. Yeah, Yeah.
Yeah, exactly. Well, to answer those. Yeah, I may. So the question is if it's possible to have multiple admin accounts? Definitely the number of accounts per platform is unlimited. No problem there. Otherwise, I cannot see anything here, and I know nothing comes to my mind, but what to add.
So just again, to reiterate that the more data there is in the registry and the more up to date, the more it will be useful to the librarians. And so. So you only need to bootstrap it as soon as possible, we need to make it. The more data there is, the more useful it will be, and we are really all looking forward to it. Absolutely so I'm looking forward to being inundated with your requests to set up your account.
And we will be sharing this recording. So if you want to share it with your colleagues, please do so. And thank you all so much for attending. Thank you much. Thank you. And Laura, and better for presenting today. Thank you. Bye bye.
Thank you. Bye-bye hey.