Name:
Collaborating to Implement Seamless Access: What Publishers, Libraries and Service Providers Can Do to Ensure Better End User Access to Scholarly Content Recording
Description:
Collaborating to Implement Seamless Access: What Publishers, Libraries and Service Providers Can Do to Ensure Better End User Access to Scholarly Content Recording
Thumbnail URL:
https://cadmoremediastorage.blob.core.windows.net/d14d1f87-2398-4e56-860b-c46b9c221bbc/videoscrubberimages/Scrubber_3.jpg
Duration:
T00H43M34S
Embed URL:
https://stream.cadmore.media/player/d14d1f87-2398-4e56-860b-c46b9c221bbc
Content URL:
https://cadmoreoriginalmedia.blob.core.windows.net/d14d1f87-2398-4e56-860b-c46b9c221bbc/Collaborating to Implement Seamless Access -NISO Plus.mp4?sv=2019-02-02&sr=c&sig=AtDnDA7lG3EE8dWKoc9fjia3HJuRMkiim4LwKXn%2FIMo%3D&st=2024-10-25T01%3A19%3A34Z&se=2024-10-25T03%3A24%3A34Z&sp=r
Upload Date:
2024-03-06T00:00:00.0000000
Transcript:
Language: EN.
Segment:0 .
PETER MURRAY: Good day, everyone and welcome to this session on Collaborating to Implement SeamlessAccess.
PETER MURRAY: My name is Peter Murray and I will be the moderator for this session. We have three speakers today. First is Heather Staines, Senior Consultant at Delta Think and Director of Community Engagement for the Open Access Data & Analytics Tool. Heather has a wide-ranging experience in the community with her most recent roles, including the Head of Partnerships for Knowledge Futures Group and the Director of Business Development at Hypothesis.
PETER MURRAY: She's a frequent speaker and participant in industry events, including the Association of Learned and Professional Society Publishers DEIA working group as the co-chair, the Charleston Library Conference, the STM Future Lab, Society for Scholarly Publishing, Council of Science Editors, the NISO Transfer Standing Committee and the NASIG Digital Preservation Committee. She has a PhD in Military and Diplomatic History from Yale University.
PETER MURRAY: Next is Julie Zhu, Senior Manager of Discovery Partnerships at the IEEE. Julie has been working in the publishing industry for 20 years. At IEEE, she cultivates and manages working relationships with providers of discovery services, link resolvers, proxy servers and search engines, as well as with libraries and consortia to maximize the content visibility, findability and accessibility on multiple discovery channels.
PETER MURRAY: She serves in NISO's ODI standing committees and the KBART standing committee and has published and presented on topics such as complying with publishing standards, reducing content gaps in discovery services, vendor-publisher-library collaborations, and metadata enhancement projects. The third presenter is John Phelps, Head of Information Technology and Collections at Coastal Carolina University.
PETER MURRAY: John has worked in academic library technology for over 30 years and is a former patent holder and co-founder of Journal Finder, the first OpenURL resolver and knowledge base to go into production in the United States. Throughout his career, John has focused on identifying and implementing innovative uses of technology in the provision of library services, online user privacy protection, and improving the user experience for accessing online resources.
PETER MURRAY: He's currently a member of SeamlessAccess access. And today we're going to start with Heather.
HEATHER STAINES: Thank you, Peter. And Thanks to NISO Plus for allowing us to present today. I'm just going to share my screen. Great, as Peter mentioned, my main day job is as a consultant with Delta Think. But for a little more than two years now, I've also done publisher outreach for the STM Association around the SeamlessAccess initiative.
HEATHER STAINES: This is an initiative that is particularly close to my heart. Back in 2009, I was part of a NISO working group around single sign on that came about to solve the challenge of publishers having different ways to indicate and signal single sign on.
HEATHER STAINES: I was extremely happy following what would later be called Ra21 and eventually SeamlessAccess to know that the work that we did back in the day was contributing to what we see as SeamlessAccess today. So why SeamlessAccess access? Well, SeamlessAccess is about improving access to online content and services for researchers. So what you see on the right side, and we've got it grayed out there, but probably will look familiar to you, is that there really is no one recognized pathway the researchers might encounter when they're trying to access through their institution.
HEATHER STAINES: There are various types of dropdowns, various language used. Talk of federations can be very, very complex. So SeamlessAccess wants to improve this user experience, whether you're on or off campus just to make it easier. And we want to work to continue the identity Federation infrastructure and standards development around that space. And also in a time where campus security can be quite a concern, we want to help improve the campus response and limit that site-wide disruption that can sometimes happen on a broad base when there are individuals or organizations trying to abuse the system.
HEATHER STAINES: So what is SeamlessAccess access? There's really three parts and I'll walk you through each of those. The first part of SeamlessAccess and probably the thing which pops into mind most readily, if you have heard of it, is the SeamlessAccess button. You can see there on the left hand side, you've got the blue button, the little SeamlessAccess logo on the left.
HEATHER STAINES: The text around Access through your institution. And this is meant to give the researchers one standard visual cue compared to that multitude of options that I showed on the previous slide. It is context aware, so you can see the name of the institution there displayed on the button and it's integrated into various service provider access flows which we will get into. So the second part of SeamlessAccess is the IDP discovery service that the user goes through when they're trying to identify their institution.
HEATHER STAINES: So on the left, you see the Find your Institution dropdown. The user starts to type the name of their institution. The different options will populate and they can select the one that applies to them. So this is standardized. It's a best practice method to find your institution. And you can actually try it out if you go to Service.SeamlessAccess.org/ds and you can look for your institution that way.
HEATHER STAINES: And finally, the third part of SeamlessAccess is a persistence service. So the user's choice of identity provider is stored in their local browser storage. This information is only accessible by SeamlessAccess. Org and approved integrators. It's completely privacy preserving and users can choose to opt out of it entirely, or at any point in the process.
HEATHER STAINES: There are different flavors of SeamlessAccess integration depending upon the type of service provider, and that's mainly publishers or platform hosts, identity federations. That allows for flexibility, depending upon what you want to do with the service. I don't want to go too deeply into the technical side of things, but we provide this handy chart so you know what comes along with each type of integration.
HEATHER STAINES: If you are a larger, more complex publisher organization, typically going to fall into the advanced category, which will allow you to include other ways that you have for identifying a user's institution and adding institutions to that dropdown. So what does SeamlessAccess look like in the wild? Here is an example. This is from the Institute of Physics Publishing page. And you can see on the righthand side that the SeamlessAccess button appears slightly below the abstract and we've blown it up there, so you can get a little bit of a better look.
HEATHER STAINES: Now, this is an example where the user has not used SeamlessAccess before. So what they see there on that button is simply Access through your institution. It's not populated with their institution yet. Once they click on that button, they're taken into the IdP discovery or that second part of SeamlessAccess that I mentioned, where they will select their institution from a dropdown list and then they're routed through their university's authentication flow.
HEATHER STAINES: So this is really important. SeamlessAccess does not do the authentication. That happens on their University site as they would ordinarily expect it to. Next time the user comes again. Sticking with Institute of Physics Publishing example, they have used SeamlessAccess and the persistence function that I mentioned remembers their choice of institution.
HEATHER STAINES: So what they see there is Access through the University of San Diego. So the button again takes them through to their authentication. I like to point out here on the left hand side, underneath the button, they can add or change an institution. Some of the research we've done on the SeamlessAccess side has shown that more users than we had anticipated do have access through multiple institutions.
HEATHER STAINES: So that can be added, and the user can toggle back and forth and it doesn't keep them from logging in through other mechanisms that the publisher or platform host may have available. The persistence works across integrators, so all participating integrators in SeamlessAccess. If you're coming via another publisher platform, this will persist and this leads to a network effect. The more publishers who join, the more beneficial it is for the researchers.
HEATHER STAINES: Now who is SeamlessAccess access? SeamlessAccess is a coalition of four founding organizations NISO, the STM Association, Internet2 and Geant. And it's meant to be a community driven effort to support that seamless access to resources, to promote collaboration, thus the name of this session, and ensure that shared research infrastructure can be sustainable and successful into the future. Currently, these are the service providers who are live with SeamlessAccess.
HEATHER STAINES: You can come to the SeamlessAccess website and for each one of these providers, we give a little bit of information on the type of integration that they have. And that example URL there to the right will take you to a page where you can see how the button works on their platform. I do recommend you go and check it out. Now ,our experience in the initiative tells us that the more options a user has when they get to a publisher page, the more confused they are about what next step they should take.
HEATHER STAINES: And on the documentation page and on user experience sections of the site, you can actually look at some of this research and find out that some sites have upwards of 11 different options to get the content. And if you're a researcher, which is the next step you should take certainly can be confusing. The placement of the button matters-- higher on the page typically is better. Details on the language or on the button also matter.
HEATHER STAINES: Very much so. Check out the documentation and that whole experience and including that IdP discovery flow matters a lot to the user. Thank you very much. We will look forward to your questions in the interactive Zoom a little bit later. And I will hand over to Julie.
HEATHER STAINES: Thank you. Here's a little bit of information about HP and HP explore. HP is the world's largest technical membership association, with over 400,000 members in 160 countries. It has a five core areas of activity publishing conferences, standards, membership and e-learning in the fields of Electrical and electronics, engineering and computer science.
HEATHER STAINES: The platform publishes anthropology journals, conference proceedings, standards, e-learning courses and hosts hosts third party content like e-book collections and the digital library. It houses nearly 6 million records and receives a quarter of a billion full text usage annually. So why did we decide to implement SeamlessAccess access?
HEATHER STAINES: Like most publishing platforms, explore supports multiple remote authentication options. We implemented Federated authentication options like shibboleth, open, Atlas and SAML a few years ago for many libraries. But for years. Federated authentication still accounted for a small fraction of all the authentication accounts. A shift occurred in 2020 during the pandemic, when the China consortia helped several Chinese University libraries set up shibboleth, the Federated access authentication counts increased significantly.
HEATHER STAINES: And we also found that users coming from Federated authentication stayed on the platform longer, visited more pages and had more text usage. Also tripoli has been on the rise 21 and SeamlessAccess advice access advisory boards for several years. We had already adopted some 21 best practices in streamlining our institutional signings search box as more publishers opted to integrate SeamlessAccess and reported positive usage increases.
HEATHER STAINES: We seriously considered implementing SeamlessAccess access, especially standardizing the button design and remembering institutions. During the planning stage, we addressed a few internal and external concerns. And first there was a concern about security and privacy. After studying the SeamlessAccess documentation and talking with the SeamlessAccess team, we learned that SeamlessAccess stores only institution, institution selection in users browsers, no personal information like name, email, logging or password.
HEATHER STAINES: It just directs users to the library signing pages. Users have the checkbox option to choose whether the browser should remember the institution. There is no real danger of insecure authentication, a SeamlessAccess place, no part in any exchange of data between the home institution and the service. This assurance helps our management decide to move the project forward.
HEATHER STAINES: The second concern was how many idps we needed to add into our institutional signing box. Many universities in Europe and the US joined single sign on Federation years ago and stored their institutional attributes in these federations. Now federations feed over the metadata attributes to education. There are several scenarios among libraries.
HEATHER STAINES: First, some libraries have put their subscription content under Federated authentication, set up a separate set of attributes and sent the attributes to publishers so that the users can use Federated authentication on these platforms to access the subscribed content. Second, some libraries have done the first two steps, but have not informed publishers.
HEATHER STAINES: Third in some institutions, libraries choose not to put the subscribed content under Federated authentication or not set up separate set of attributes. And fourth, some libraries only rely on easy proxy for remote authentication. On the publishers side, some publishers, including HP, was still counting on libraries to send requests for setting up preferred authentication.
HEATHER STAINES: For various reasons. Percentages of libraries that have set up a Federated authentication are high in some European countries, but low in the us, Canada and some other countries. A multiple campaigns, two libraries received a few responses. During the pandemic, some publishers chose to download metadata from educating and load it to their institutional signing box.
HEATHER STAINES: We talked to multiple publishers and librarians to understand their perspectives, and we also conducted several user authentication journey tests. Then we decided to do two pilot projects, first, adding 40 Plus Canadian University library idps into the Explorer institutional signing box. And second, adding easy proxy URLs into the Explore institutional signing box for libraries that do not use Federated authentication.
HEATHER STAINES: We decided to implement SeamlessAccess before adding more idps or easy proxy URLs. The third concern was whether we had enough resources to implement SeamlessAccess in house. Since I tropics explore is a large, complex platform. We decided to choose the advanced level so that we can have some control over customizations. After talking with publishers, they had used third party party help for implementing SeamlessAccess.
HEATHER STAINES: We decided to do the work in-house. We study the SeamlessAccess documentation guidelines on buttons, discovery and persistency, and we also studied the examples from over a dozen other platforms. Then we assembled our user experience design team to decide what customizations we would need on the platform. And we decided to add the institutional sign in button on the article page and also on the global header.
HEATHER STAINES: On our institutional discovery form, we decided to include a link to the institutional username password option still used by some corporate customers. We decided to allow the browser to remember multiple institutions. We created interactive design prototypes and met with the SeamlessAccess team for design review input. The SeamlessAccess team also offered quick feedback when our technical team needed help setting up APIs.
HEATHER STAINES: We did several rounds of user authentication testing during this stage and also after the launch. With help from the SeamlessAccess team, we successfully launched SeamlessAccess in our production production expo platform in early October 2020. 2022 when we were planning to implement SeamlessAccess access, we also considered how to track and assess impact.
HEATHER STAINES: We decided to tag all the SeamlessAccess buttons to see how often these buttons were clicked by whom and in what countries. The first chart shows how many daily visits and unique visitors clicked the access buttons on accessed via your institution from your institution buttons either from individual article pages or on the global header. In October, right after the launch, we saw around 21,000 visits involving SeamlessAccess per day.
HEATHER STAINES: We realized that we missed the taglines on some pages and we made some adjustments in the next release in November. And immediately we saw the trackable things. Excess visits increased to 40% 40,000 per day doubled. When broken down by countries. Over 30% of these visits came from China, followed by India, the United states, UK and Germany.
HEATHER STAINES: We also wanted to check if Federated access authentication counts times increased after the SeamlessAccess launch and by how much in top countries. Here are the results of the first three months from October to December 2020 to. Overall, comparing 2021 and 2022 Federated authentication accounts increased 62% just in Q4.
HEATHER STAINES: From October to December, if broken down by month, the increase is 77% in October, 60% in November, and 52% in December. If broken down by country, the increase is 61% in China, 60% in the us, 23% in UK, 36% in Germany, 16% in India. Remember 2022, we did not add a significant number of library idps from these countries because not many approached us.
HEATHER STAINES: Reach out to us on that. But we did a pilot project of adding 40 Plus Canadian idps. Now, surprisingly, the largest authentication times increase was from Canada, 256% It is evident that the SeamlessAccess project is a success. It has significantly increased the Federated authentication times across the globe.
HEATHER STAINES: The increase would be even more significant if we added more idps to the search box. So our next step is to add more idps from more federations to our export platform for libraries that are not using shibboleth open, we will add more easy proxy signing URLs and figure out how to remember these institutions in the browsers, even though the current SeamlessAccess service does not support easy proxy.
HEATHER STAINES: Identifying and adding idps is still a tedious process. So we'll be happy to work with the industry to figure out efficient ways to do that. Again, we think the SeamlessAccess team for your patients and guidance throughout the process. We also thank the publishers and libraries that offered tips and provided input when we worked on this project. OK so I think I will pass the torch to John.
HEATHER STAINES: OK thank you again, Julie, and thank you previously to Heather. I'd like to offer a librarian's perspective concerning the challenges to implementing Federated access, the benefits that Federated access brings to libraries and to their end users and their research experience, and how SeamlessAccess makes Federated access even better.
HEATHER STAINES: Well there are some challenges for libraries in implementing Federated access. However, None of these, in my opinion, are insurmountable. But they are real, honestly, in general. First up is just my. Based on my experience, many librarians not only don't want change, but they openly resist it. I've been in academic library technology for quite a while now, and a significant part of my job has been change management.
HEATHER STAINES: Basically trying to calm perceptions and fears regarding how a new technology or platform implementation will change existing workflows and procedures specific to Federated access and technology platforms. Most libraries that are still using IP based access typically through easy proxy fail that they don't have the personnel, the expertise or even the money to undertake moving to Federated access. So I only break these out for you just a minute.
HEATHER STAINES: Specifically to personnel. Most libraries these days are in a state of contraction post COVID and spaces, resources and personnel. There were significant reductions in forces during covid, a personnel who won't be rehired. Also, early retirements were incentivized as well. So in general, our ranks are thinning some.
HEATHER STAINES: Also pertaining to expertise. Very few libraries, in my experience outside of our ones, have the in-house expertise to manage such a change. But I will say that since epsco partnered with OpenAthens and you are thinking about becoming an OpenAthens customer, or already are that the process for implementing OpenAthens has become consistently easier and the timeline shorter. They've helped a lot.
HEATHER STAINES: I remember early presentations. People were talking about a year or a year and a half even to implement Federated access, specifically OpenAthens. And we went live about a year and a half ago at Coastal Carolina university, and it took us about three months. We were going speed, but still we did it in about three months.
HEATHER STAINES: Let me jump over to the cost considerations. You know, if you'll recall, walk down memory lane with me, easy proxy was famously about $325 for years and years until oclc bought it out from Chris zager. And even with consistent increases, it's still priced at around $700 or $800 for a locally installed instance of easy proxy. I don't know how much it costs out in the cloud these days, but open Athens, on the other hand, is typically at least several thousand annually to subscribe to.
HEATHER STAINES: So I think I can say all that without getting in legal hot water. So and then lastly, relationships with that can be a barrier as well. A lot of times librarians have poor or even nonexistent relationships with their campus department as opposed to vital partners in the organization. Many times were seen as just, well, just another pain in the neck.
HEATHER STAINES: You know, it's just another department that they have to support. And not only does this serve as an impediment to the library for rolling out new technologies it creates, who knows the opportunities for communication and collaboration that were missed along the way. So, you know, at least in my opinion, I think it's vitally important to have a good working relationship with your campus IT department.
HEATHER STAINES: So that you can advocate for users, advocate for user privacy and to speak to the general needs of the library. Just anecdotally, I asked for a meeting with our campus department of several years ago. Now, due to numerous major communication problems that were occurring that were causing catastrophic failure to some of our technology platforms.
HEATHER STAINES: And so but after that meeting, I'm pleased to report that it was a very collegial meeting. And as a unforeseen byproduct of that meeting, we now meet annually, twice a year, and they've proven to be very productive. And we eliminate problems in a hurry and we eliminate some problems proactively before they even really become a problem at a broader scale. Of course, I will say it didn't hurt that we I brought lots of coffee and donuts to the meeting as well.
HEATHER STAINES: And that sort of grease the wheels a little bit for us. So let's transition over to benefits of Federated access. It utilizes a more reliable, robust, SAML based infrastructure that helps put libraries in control of privacy because the institution decides what user data, also known as attributes, are shared with a vendor, if any. Also consider that when compared to easy proxy, ongoing maintenance of this environment is a lot simpler since the specific information necessary to establish trusted connections lives in a Federation accessed by identity provider and service provider alike.
HEATHER STAINES: It also provides support for researchers who might be affiliated with numerous institutions or research organizations, which Heather touched on a little bit earlier. Seldom will that be the case with an undergrad student, but frequently it's the case that a user would need to change their affiliation if they were, say, an adjunct faculty member. They might have access to a particular resource with one affiliation, but not another, and they need to switch over in a hurry.
HEATHER STAINES: And SeamlessAccess supports that. Also consider that. It improves the campus response to security incidents, which Heather also touched on earlier. I think this is because it's much easier to ascertain the specific compromised account or with IP filtering. Many times the vendor shuts down access to an entire IP range and then tries to locate that specific user that may have been compromised.
HEATHER STAINES: So that's sort of a blunt tool, whereas Federated access is more of a surgical technique to get rid of that bad actor. And lastly, and I suppose very importantly to librarians. Federated access also offers a far better user experience that provides authentication at the point of need. You know, IP authentication is very counterintuitive to the current research user experience because it forces researchers to start from or at some point circle back through the institutional portal, you know, to pick up a proxy prefixed URL before they can access the online content to which they are rightly entitled.
HEATHER STAINES: And this is contradictory to the way discovery works, and it degrades the overall user experience. And just needlessly complicates things, you know. So if you will, let me briefly expound on this concept of authentication at the point of need based on some recent findings at my home institution from when Coastal Carolina University migrated from easy proxy to OpenAthens last August a year ago.
HEATHER STAINES: We re encoded or what they call athenz using all the resource links in our Z list and discovery platforms and went live with OpenAthens on August 16th, 2021. However, the infrastructure, unbeknownst to me, didn't even realize that this was the case. It was already in place and functional. Come to find out on July 22 that it was completely hidden to our users. I would just.
HEATHER STAINES: Getting used to the OpenAthens interface on the admin side and looking at the usage dashboard. And I noticed that we started seeing a lot of inbound traffic and successfully authenticated sessions. There were. I'm going to have to check my notes. There were as many as 1512 successfully authenticated sessions in that time period, with as many as 137 sessions a day.
HEATHER STAINES: I mean, how could this be since all of our lengths were still using easy proxy as a proxy prefix? Well, the only possible answer is that users were accessing resources via the wayfinder service on each vendor's platform that they landed on after having started their research journey from the open web. Google Google Scholar. Who knows?
HEATHER STAINES: But they were able to intuitively log in with no help or intervention from library staff. And I sit-in the chair that would receive those problem calls, and I received None during that time. And if you look on the slide, it does show the actual successfully authenticated sessions that we experienced during this time. So it's pretty fascinating and is very exciting to me after years of years and years of having, you know, encountering reports from users who could not authenticate remotely.
HEATHER STAINES: As often as not because they did not come from a proxy prefixed URL. To be able to have to support access from the open web was very exciting to me. So having talked about the challenges and the benefits of Federated access, I thought I'd expound a little bit on what Heather showed you earlier and give you a brief demo. It's not a live demo.
HEATHER STAINES: It's based on slides. But I'll walk you contextually through the user process from beginning their research open on the upon the open web, out on the open web. And going through various sites just to encounter what the user will see when they land on these different platforms. So in this use case scenario, the user began their search out on the open web began be that Google Google Scholar wherever they happen to start their research from.
HEATHER STAINES: And they located a journal article that resides on the ACEs platform that they'd like to read and notice in the center of the screen the access to your institution button. This is the SeamlessAccess button and it is a very consistent call to action across all websites that have implemented SeamlessAccess. So when we click on the link, we are pass through to the ADP discovery service or the wayfinder.
HEATHER STAINES: It's also called and it autofill, so you don't have to tediously type in the entire name of your institution. In this case I was typing in coastal and it. Brought up far fetched for me, Coastal Carolina University. Once we've identified the institution or the organization with whom we'd like to be affiliated, then that pipes us through local authentication. In my case, Coastal Carolina university's.
HEATHER STAINES: And then it loops us back around and you see that we now have full text to this particular article and I blew that up for you. The upper if you didn't know from being able to see the full text, then you would also be able to identify that. You were now successfully authenticated because access provided by Coastal Carolina University in the upper right hand corner of the access platform.
HEATHER STAINES: So the user in this use case, they read the article and scrolled through it and came down to the bottom of the page where all the references were. And they located another journal article that they think they would like to read the full text on. So number 11 in this example from, from this particular site and. It doesn't matter which link you happen to click on, it's different pathways, but the end result is always the same.
HEATHER STAINES: It'll loop you back around to the vendor's platform and then again you'll encounter SeamlessAccess. So let's just say that the user clicked on Google scholar, pass through their search interface and then landed on this particular journal article, which was in the references. And this one happens to be situated on the ScienceDirect platform as opposed to asrs. Now notice again the consistently placed access through Coastal Carolina University.
HEATHER STAINES: So as was mentioned earlier, persistence was established when we first affiliated and it follows us now through the rest of our journey unless we change that affiliation because that information is stored in local browser storage. So we simply click on the Access to Coastal Carolina University button. It seamlessly, possibly seamlessly passes us through local authentication.
HEATHER STAINES: And then we are taken right back to the site where we can either read the full text online or we can download the PDF. So that is how persistence is established and follows us from site to site. Now consider also that let's say let's continue on with this particular user journey. And the user also had a citation and they wanted to see if there was full text availability.
HEATHER STAINES: So they just plunk it into Google, the Google search interface and it just so happens it is and it happens to reside on the nature platform. And clicking on that link takes us to the nature platform, to the full text article. And notice again access this article. In my case, Coastal Carolina University. And again, there is the SeamlessAccess button access to your institution.
HEATHER STAINES: Well, in this case, we would click on the particular the SeamlessAccess button and then we are piped through once more seamlessly to a fully authenticated session. Watch out without having to tediously enter all that information again to authenticate. And that's one of the major benefits of SeamlessAccess access, is that without that service. He will be landing on all these various different vendors platforms, and there would be no consistent call to action.
HEATHER STAINES: All the flavors would look different. And what a user would have to do which buttons they need to click on, how do they go through a wayfinder and are recognized and can get to the access? I'm sorry, get to the full text journal article by accessing it through whatever mechanisms they've brought them to bear so far. So that in essence is a basic contextual user journey of what a user might see when they're bouncing from platform to platform seamlessly and accessing the full text information to which they are rightly entitled.
HEATHER STAINES: So I guess I would close by saying that. If you'd like more information regarding how Federated authentication works, please visit the SeamlessAccess website at SeamlessAccess. And in the upper right hand corner, you'll see where it says Learning Center. And there's a whole lot of helpful resources there, including an overview that's of Federated authentication that's intended for a non-technical audience.
HEATHER STAINES: So it's a pretty easy read. So thank you for your time. And we'll. Stop sharing.
PETER MURRAY: Great thank you, Heather, Julie and John. This concludes the prepared recording part of the session. We'll now move to the interactive part of the session for reactions and discussions of these topics and related ideas. One of the things we'll be doing at the end of the discussion session is to identify one or two main ideas as NISO identifies areas of new standards, best practices, publications and educational topics.
PETER MURRAY: We also want to find people who are interested in taking ideas and drafting more concrete proposals for the NISO topic committees to consider. So as we enter the discussion phase, think about how you might join in that effort. With that. We'll close out this recording and we'll see you in a moment.