Cadmore media player playing video Centering interoperability in the future of library-based publishing -NISO Plus
Video Player
Accessibility
Using forms mode, you can utilize keyboard shortcuts to make usability more efficient.
Space bar will play and pause the video. Pressing escape will close all displays and pressing it again will jump to the end of the player.
You can press A to open the Keyboard Shortcut Dialog which also provides an audio description of the player and all of its features.
Language
1x
Play Speed
Adjust Volume
Transcript
Search
Result Count
of
Click to jump to result
Search
Re-center
Segments
Result Count
of
Click to jump to result
Search
Name:
Centering interoperability in the future of library-based publishing -NISO Plus
Description:
Centering interoperability in the future of library-based publishing -NISO Plus
Thumbnail URL:
https://cadmoremediastorage.blob.core.windows.net/6b66fea4-1973-4589-b546-2b46a2212c97/thumbnails/6b66fea4-1973-4589-b546-2b46a2212c97.png?sv=2019-02-02&sr=c&sig=716C58%2BcoQYXawcItODQpgmrsbqH7%2FqJIlgHyAngHck%3D&st=2024-12-22T05%3A17%3A33Z&se=2024-12-22T09%3A22%3A33Z&sp=r
Duration:
T00H48M43S
Embed URL:
https://stream.cadmore.media/player/6b66fea4-1973-4589-b546-2b46a2212c97
Content URL:
https://cadmoreoriginalmedia.blob.core.windows.net/6b66fea4-1973-4589-b546-2b46a2212c97/Centering interoperability in the future of library-based pu.mp4?sv=2019-02-02&sr=c&sig=qS3FtC5hRLpJDAcd4xVWTbUpmJJ2a66AnyCCpHjVWSs%3D&st=2024-12-22T05%3A17%3A35Z&se=2024-12-22T07%3A22%3A35Z&sp=r
Upload Date:
2022-08-26T00:00:00.0000000
Transcript:
Language: EN.
Segment:0 .
[MUSIC PLAYING]
TODD DIGBY: Welcome. My name is Todd Digby and I'll be the moderator of today's session. I'm the department chair of the Library Technology Services Department at the University of Florida. Today's presentation is titled "Centering interoperability in the future of library-based publishing." And as a look at the next generation library publishing project are NGLP. NGLP is a collaborative initiative of Educopia, California Digital Library, Strategies for Open Science, or Stratos, and the Confederation of Open Access Repositories, and is funded by Arcadia.
TODD DIGBY: Today, we are pleased to have Sarah Lippincott from Educopia, where she serves as the product owner of the Next Generation Library Publishing project; Kristen Ratan, the founder of Strategies of Open Science, or Stratos; and Catherine Mitchell, who is responsible for overseeing the strategic planning development and operational management of the California Digital Library's Publishing, Archives, and Digitization project. I will now turn it over to Sarah.
SARAH LIPPINCOTT: Thank you for having us, Todd. We're excited to talk to you about NGLP. I'm going to share my slides. As Todd mentioned, NGLP is a collaborative project. We have brought together stakeholders from Educopia Institute, the Confederation of Open Access Repositories, Stratos, the California Digital Library, to lead a project that is centered on values and principles that has values and principles at its core to develop software governance structures and service models to empower next generation library publishing.
SARAH LIPPINCOTT: So today, we're going to talk about our two interoperable standards-driven software components and the pilot implementations of those components that will bring our software-- our interoperable modular publishing stack-- to life. So a little bit of background on our project. Small, mission-driven digital first publishers, which include library publishers but also university presses or independent scholar-led presses, have a growing influence on scholarly communications, and they have over the last couple of decades.
SARAH LIPPINCOTT: The 2022 Library Publishing Directory, for example, counts 143 library publishers around the world actively publishing over 1,200 journals and who collectively issued over 1,600 monographs last year. These library publishers range from small liberal arts colleges, who are publishing maybe a handful of journals, to large universities and consortial initiatives building expansive portfolios of journals, books, learning objects, gray literature, experimental media, and other types of content.
SARAH LIPPINCOTT: Yet these publishers, despite the growing momentum and their growing influence, have had limited options when it comes to publishing technologies platforms and tools that meet their unique needs as library-based publishers. The NGLP's community engagement efforts over the past 18 months-- or two years, at this point-- have identified remarkably consistent needs, even across this very diverse field of different institutions and different contexts.
SARAH LIPPINCOTT: And NGLP emerged to address those needs. So we found that library publishers want to continue working with the familiar and functional open-source publishing tools that they already use. They don't want wholesale replacement of the publishing tools that work for them already. Rather, they want modular infrastructure that builds on top of what already is working. They want, however, a seamless, integrated user experience across these platforms, allowing for robust management and use of the entire diverse portfolio of library-published content.
SARAH LIPPINCOTT: In particular, library publishers told us that they see a need for unified web delivery that unites content from multiple sources. For example, a journal submission and review system and an institutional repository into a single, modern, flexible discovery and display platform. They want to continue to take advantage of the submission and curation tools that are optimized for different types of content, like OJS or Janeway for journals, and DSpace for institutional repository content like theses and dissertations, while also building a portfolio that reflects the full range of their scholarly and creative output.
SARAH LIPPINCOTT: Library publishers identified this platform, this kind of unified platform for display of journals and institutional repository content, as particularly mission critical. But the lack of available options for assembling this type of portfolio and managing this type of portfolio has led to two frustrations-- has led to library publishers feeling barriers to growth, and has also led to limited choice and vendor lock-in.
SARAH LIPPINCOTT: So the NGLP team believes that open-source software represents the best alignment between library publishers, their core values, their missions, and the way that they operate. But open-source software is really resource intensive to build and maintain. Many institutions, particularly small library publishers, lack the human or financial resources to implement open-source software.
SARAH LIPPINCOTT: So NGLP's goal is to make open-source software for publishing accessible to a range of institutional contexts and sizes by building not only these software components, but by developing a service provider network, a range of service models for providing a hosted and turnkey version of the NGLP publishing stack that is based around community, accountability, and trust, and that offers a la carte services that meet a range of different library use cases, and also allows institutions that do want to host software locally to do that as well and participate in a vibrant community of practice.
SARAH LIPPINCOTT: So now I'd like to ask Kristen to talk a little bit more about the way that we are building this community and how we will bring our code to life in the next phase of the project.
KRISTEN RATAN: Thanks, Sarah. That was a great introduction. When we started and embarked on this journey, which was now a couple of years ago, and kind of crafted what we thought this project needed to be we're really grateful for Arcadia to fund us to basically build a solution space. So when we began this process, we thought, what is it that the community really needs? The first thing one thinks of is, we need a new tool.
KRISTEN RATAN: We need a new platform. We need this one, single solution that will create all of the change and all the goodness that we think we need. In fact, when we embarked on this, we spent the entire first year of the 2 and 1/2 year project asking the community what they needed. And this was an excellent exercise because it moved us through this idea that there's some single solution out there to this idea that we need a really modular, interoperable set of solutions.
KRISTEN RATAN: What we needed to offer people was choice. And people were feeling very locked into things that they've made choices about in the past, and there wasn't a lot of flexibility and there wasn't a lot of ability to move from one thing to another. So we focused on choice. And what the library publishing community told us was there are a lot of things that are out there in the open-source world in publishing and in IR land that we are very happy with.
KRISTEN RATAN: These things should not be replaced. We don't want some new thing to come and sort of pave over all of the things that have been built before. What we want are-- we want any new development to fill specific gaps that we've identified, where there isn't a solution at the moment that's exactly what we want. But more than anything, they said, as Sarah alluded to, we need trusted service providers.
KRISTEN RATAN: We need service providers that also have those values and principles at their core and that will work with us to create sustainable solutions over time. Many libraries that are hosting their own open source are looking to move away from that. They're actually looking to outsource more than they had in the past. And those who are using outsourced solutions we're looking for values-driven ones and options there.
KRISTEN RATAN: So we consider this a problem space that needed a full solution space. And that's why the project has focused on everything from values and principles and what does it mean to be mission-aligned through what should the governance structures and business models look like between open source tools providers and service providers, how do you create that service layer as a full ecosystem.
KRISTEN RATAN: So you'll see we have a technology component, but that is by no means the only aspect of what we're doing. We're going to look at the technologies that NGLP has sponsored to be built. There are two in particular that are at the core of this and they're excellent pieces of technology. But we looked at how can they fit into this larger ecosystem. How can we make them interoperable with existing tools and platforms that people are using?
KRISTEN RATAN: We listened carefully to the library publishing community, who said in particular they're very happy, some of them with their OJS installation, or they're trying Janeway. Those are trusted, open-source platforms that they're using. There are any number of wonderful IR platforms, like DSpace, that they're using and they didn't necessarily want to make changes there. But we listened to what are the gaps that they needed filled, and then we'll talk about what those are.
KRISTEN RATAN: The second piece of this was that service layer. And so the way we've done that is we've talked to a number of service providers who work actively in this space-- and some of them we saw on the slide earlier-- and we said, can you step up and assemble a solution that includes technologies you've worked with in the past but also these new components that we're building? And it was amazing to see the response.
KRISTEN RATAN: Just like we'd gotten a really, really positive response from the library publishing community as we did the outreach, we had an equally enthusiastic response from potential service providers who were looking to meet a broader set of needs than they had done thus far. And so in light of that, we decided the best way to get them up and running was to set up pilots. And we are launching with three pilots coming up shortly, and we'll talk a little bit about that in a minute.
KRISTEN RATAN: But in addition, we see this as a way of making continual improvement all along the way. So new pilots will be launching after that, with people who are maybe interested in creating a different assembled solution or meeting a different market need. So that kind of flexibility is, we feel, essential to be able to create sustainable service models moving forward.
KRISTEN RATAN: Sarah.
SARAH LIPPINCOTT: Thanks, Kristen. So I'm going to talk to you more about the specific components that we're building. The NGLP team is partnering with Cottage Labs and Cast Iron Coding, two really amazing development partners who are building two open-source software components that will be licensed under an MIT license and available for anyone in the community to adopt, including the pilot service providers that we are bringing on as part of NGLP project to test out both the technology and service delivery.
SARAH LIPPINCOTT: So the first component that we are building is a web delivery platform for unified content discovery and display, which is based on the specific feedback that I mentioned, that Kristen mentioned as well, that library publishers want us to take modular components-- take components that they already use in their workflow and knit those together into an end to end platform that meets their needs for library publishing. The web delivery platform is designed to support multiple upstream submission systems, such as Janeway, OJS, and DSpace, aggregate content from them into a unified discovery and display platform, and allow administrators to mix and match content into different collections, customized templates for different community pages, and all while supporting a single public-facing access point to the rich portfolio of content that they're assembling.
SARAH LIPPINCOTT: So you can see here that you can have journals running through Janeway or OJS, for example, and we'll be demonstrating this workflow in one of our pilots led by Janeway to submit articles through Janeway and have them appear in the web delivery platform as the front end, and combine it with content that comes out of an institutional repository platform, like DSpace, into a single, unified portfolio.
SARAH LIPPINCOTT: This was something that was identified as extremely important to our library publishing community and they wanted something that allowed them to be flexible, to evolve over time, and to continue to work with the tools that they're already using. We want this software component to be flexible, content-agnostic, work for a range of scales and contexts of library publishing, and we wanted it to rely on standards and structured data to ensure machine readability, data portability in the future, and interoperability with these upstream systems.
SARAH LIPPINCOTT: So the data structures in the web delivery platform, to that end, are not hard-coded, but are defined by JSON schemas. This provides a lot of flexibility for the platform while also ensuring that content is machine-readable and portable. The web delivery platforms API-based front end, which I'll demonstrate for you in a moment, is powered by-- provides access to and is a first class consumer of a machine-readable-- sorry, a GraphQL API, which allows the web delivery platform itself and other applications to query and mutate the stored data.
SARAH LIPPINCOTT: And because the web delivery platform is a first class consumer of its API, it's built upon a framework of structured data. The structure can evolve over time and the front end can be modified-- frontend templates can be modified to accommodate new data points, new views of data, so it can support an evolving array of content. And configurable content schemas defined in JSON allow the WDP to move from generic entities into recognizable types of content, so moving from collections and items defined in the abstract, to journals, articles, books, and build metadata schemas that are appropriate for different content types.
SARAH LIPPINCOTT: So these schemas not only govern content but also components on a page display within different templates so that you have appropriate context for a range of different content types, whether that's IR-type content, theses and dissertations, or whether it's journals, that you have templates that make sense for the type of content you're displaying, and you can have disparate content types unified in a single system that are searchable side by side, but displayed in templates optimized for their content.
SARAH LIPPINCOTT: So what we've developed is not just a front-end display, but really a publishing framework that's content-agnostic and scalable. Closely coupling presentation to the content schemas also allows the web delivery platform to avoid the kind of generic rendering and UX that kind of characterizes a lot of institutional repository software. And in future iterations of the WDP, we hope to include interfaces that will allow developers to package these presentational components and metadata schemas as reasonable or adoptable plugins that could be shared between institutions.
SARAH LIPPINCOTT: So by developing these schemas, by developing this kind of publishing framework, we're also seeding a community of practice around the web delivery platform, where you can have communities sharing their own contributions back to the software. We're also providing built-in support for controlled vocabularies for taxonomies like credit, for example, incorporating persistent identifiers, ensuring we have DOIs and ORCIDs being a core part of how data is stored and displayed.
SARAH LIPPINCOTT: And we envision a lot of exciting possibilities in the future as the software develops for integration with services like ORCID. And we're relying on standards to pull in information into the web delivery platform. So we are using OAIPMH to pull in metadata and content from all of the systems into the web delivery platform. So we're pulling in metadata in standard formats from an OAIPMH feed, and we're also able to pull in JATS full text, where it's available, from systems like Janeway so that we can have the dynamic-- so that we can have HTML display of full text where it's available, which is something that is an aspiration for a lot of library publishers to begin investing more in HTML display and moving a little bit away from PDFs.
SARAH LIPPINCOTT: So I'm going to do a new-- I'm going to share my screen and give you a look at the web delivery platform. So as you can see, the web delivery platform allows multiple communities to exist side by side, communities being the kind of top level collection in our schema. This use case is something that Kathryn Mitchell will describe further, that is ideal for library consortia, for example, to have different partners or different stakeholders having their own kind of space within a single instance of the web delivery platform.
SARAH LIPPINCOTT: But it's also a way that any library publisher can create these kind of top level collections. We're going to take a deeper dive into one of these collections. You can see we get a few nice stats right off the-- right on the front page to give a sense of how lively and vibrant these different communities are. Each community has its own dedicated landing page that can have its own logo and imagery to give it its own look and feel.
SARAH LIPPINCOTT: In the future, we plan to offer more customizations to these community templates so that different communities could really differentiate themselves from one another and have more variety and more choice for different communities to customize things like colors and fonts. Communities can choose content to highlight on the home page. Here we have a number of journals, one of which has a cover image that was uploaded and the rest have cover images that were actually generated algorithmically within the web delivery platform.
SARAH LIPPINCOTT: So you get nice imagery even if you don't have a-- If you don't have somebody selecting a cover image for everything, the system will generate one for you. And we'll take a look at one of these example journals. So we're drilling down through content here. So each journal landing page, again, can be customized. So this is-- let's actually go back to the journal content.
SARAH LIPPINCOTT: So you can see, this one has been filled out with more metadata. We can see how it's licensed, whether the articles are peer-reviewed, other important metadata right up there at the top. We can have a hero image in these templates. There's a wide range of customizations that we can make to any kind of journal page. And again, all of this is powered by those schemas, so it's very flexible and dynamic, and these templates can change and evolve over time, as needed.
SARAH LIPPINCOTT: And content can be presented in different ways. So we can have content from the current issue automatically highlighted on this journal landing page. We can also browse all issues of a journal. We can browse related journals. We can browse all of the articles. So all of this content is very flexible, can be mixed and matched and presented in a range of different ways. On an article page, we have the ability to post full text HTML when it's available alongside metadata information about contributors, which are their own entities.
SARAH LIPPINCOTT: So if we click on a contributor, we can see all of that author's publications, again, generated from-- dynamically populated. And we have a placeholder here for embedded metrics, which will be coming from the second component, which I'll describe in just a moment.
SARAH LIPPINCOTT: And finally, we can use this picker up here to select different communities and kind of navigate through different areas of the web delivery platform. We're currently working on Search as well, so we'll have cross-platform discovery, again, facilitating the ability to have communities that have primarily journal content and IR content living side by side, giving all of that content excellent discoverability, really polished, modern presentation that puts all of this content, really showcases it, and puts it on equal footing.
SARAH LIPPINCOTT: And finally, I'm going to share the NGLP's other component being developed by our partners at Cottage Labs, which is an analytics dashboard. So going along with our web delivery and display of content, our community told us that they really needed robust metrics that would give them insight into and oversight of managing this content portfolio.
SARAH LIPPINCOTT: They need insight into how publications are moving through the system before they are published, and then they need post-publication engagement and readership metrics. So the analytics dashboard uses-- I've lost my window with slides.
KRISTEN RATAN: While you're looking for that, Sarah, I'll just mention that what's exciting about the analytics dashboard is the ability to pull analytics from multiple platforms, existing platforms like OJS or Janeway or DSpace, as well as the new web delivery platform, and being able to unify those in a single place, which has been a struggle, frankly, in publishing for a long time. So this is a really exciting solution and it's a standalone solution that could be applied to anybody else's platforms out there.
SARAH LIPPINCOTT: Absolutely. So just to give an image to what Kristen is mentioning, so we are aggregating workflow metrics. Much in the same way that the web delivery platform is aggregating content from these upstream systems, we're aggregating workflow event data with usage event data into a series of dashboards that are customized for different stakeholder groups.
SARAH LIPPINCOTT: The dashboard uses a custom JavaScript framework developed by Cottage Labs to generate these dynamic visualizations. And for the RMVP release, the dashboard is capable of harvesting data from Janeway and from the web delivery platform, but we intend for it to be able to harvest data from multiple upstream systems. And a data archive that underlies all of this allows administrators to go back to the raw data as it's harvested, before it's normalized for presentation in the dashboard, ensuring that there's access to data in case of any questions about integrity.
SARAH LIPPINCOTT: And we want all of these metrics to be traceable and transparent. Our metrics are not currently counter compliant, but we aspire to provide robust and very granular metrics that stakeholders can drill down into, can build their own reports, ultimately, and can export data in multiple formats for further analysis as well.
SARAH LIPPINCOTT: This report shows engagement metrics. So this is post-publication engagement. We're pulling in data, in this case, from the web delivery platform. You could envision pulling in event data, usage data, from multiple systems, but our primary consumer for the post-publication metadata for our pilots will be the web delivery platform itself.
SARAH LIPPINCOTT: And this dashboard allows all of the-- provides all the capabilities that library publishers want, that you kind of expect from an analytics dashboard-- the ability to filter or to limit by a time range, by different types of interactions, by different content formats within the repository. We provide a map of engagement geographically, and the map also serves as a navigation mechanism.
SARAH LIPPINCOTT: So as you zoom in on the map, these graphs adjust dynamically so that you can see more specific information related to how content is being engaged with in different parts of the world. And we can see our download formats in an interactive bar graph down here as well. So this is the engagement report. We've also-- or engagement dashboard.
SARAH LIPPINCOTT: We've also built a dashboard for workflow metrics. I want to leave time for us to talk a little bit more in-depth about the pilot implementations of these software, so I'm not going to demonstrate that one at this point. But we are really proud of the work that both of our development partners have done, that has been deeply informed by our community engagement work that we've continued throughout the development process, and we're really excited to put these to the test during our pilot implementations.
SARAH LIPPINCOTT: So Kristen, can you give us a little bit of-- can you start us off talking a little bit about how we'll bring these to life over the next few months?
KRISTEN RATAN: Absolutely. And I do want to-- shout out to Cast Iron Coding and Cottage Labs, who have been our technology partners. It has been a pleasure working with highly competent, very highly motivated, and very creative partners, both of them. And they've each brought different things to the table. But one thing that both of these dev shops have demonstrated is a commitment to using standards and commonly used tools, softwares, et cetera, the whole way through.
KRISTEN RATAN: So this is important in library publishing, where things have not always been up to the kind of publishing standards that many of us are used to. And so now we are able to offer software solutions and services that give all the content DOIs, for example, or can collect ORCIDs, or can show counter compliance statistics that utilize OAIPMH and be able to contribute back to those standards as well.
KRISTEN RATAN: So this is a really exciting way to move forward. And the pilots that we are launching are really the demonstration cases for this. So this is sort of where the rubber hits the road. We get to the exciting part. We want to show that we have scalable solutions and we're testing real world implementations. So we have three pilots that assemble these modules into the end to end services that people need, and we're working both with technology and service partners to make this happen.
KRISTEN RATAN: And it gets a little confusing because sometimes the technology partner is also a service partner. So other use cases in content types are on the roadmap, but for the moment, we're starting with what the community told us they wanted the most, which was a combination of IR and journals, or journal-only solutions. So people have a lot of ways to do IRs only. This idea was really about how do you help those libraries that are also publishing journals, and then eventually things like books and OER?
KRISTEN RATAN: So this is our starting point. We have three pilots. The first one is demonstrating what a sort of turnkey hosted journal plus IR solution would look like, that builds on this particular one, uses Janeway as its manuscript submission system, a headless Janeway. A content then flows into the WDP so that it can meet up with IR content that may have come, from example, from DSpace or other IRs, and be displayed alongside-- so journal and IR content can be displayed together in the web delivery platform and then the analytics dashboard is able to pull analytics from both the manuscript submission Janewayside, as well as the web delivery platform side.
KRISTEN RATAN: So this is a unified IR plus journal solution that was really one of the leading requests that came out of our community engagement. So we're super excited about that. The second is a CDL-run pilot. So CDL has always been, from the beginning of this project, an exemplar for us as a way that library publishing can combine various content types and have that unified display that you see on eScholarship, CDL's platform.
KRISTEN RATAN: In CDL, as one of the key partners here-- and Catherine is one of co-PIs-- was very eager to say, OK, how can we improve our own digital library, essentially, and how can we use these open source components and be able to combine them and create interoperability within our own implementation? So CDL is testing these modules, which has been fantastic. CDL is testing, for example, the DSpace to WDP flow, which is great; and how the analytics dashboard will work, whether a WDP can be swapped in for what they're currently using.
KRISTEN RATAN: And then the third is a journals-only pilot. So this meets the use case of when somebody's got other needs met elsewhere, but they really need a new, modern, well-functioning, hosted journal system that really can rival what other journals are doing out there. And so this one is being run by Longleaf Services, which is a non-profit subsidiary of the UNC Press. And they'll be working with the campuses there in the UNC system.
KRISTEN RATAN: And they're running Janeway as their manuscript submission system and the web delivery platform as their display layer, with the analytics dashboard being able to pull from both. So those are the three-- and they have-- as I mentioned, they have constituents within the UN system that are eager to jump in and do this trial. Janeway for that pilot, the journal plus IR. We have a number of library publishers very eager to participate.
KRISTEN RATAN: And I think we'll probably have about five. We'll be launching these pilots at the end of March, first week of April time frame. And we'll be able to run them as real experiments. We have acceptance criteria lined up. The pilot partners will test and try this with their own content, with their own data, and be able to give us really detailed feedback. The pilots will run a few months, and then we'll have a report out on how things have gone.
KRISTEN RATAN: So this is really exciting because it's really the fun part, where we get to see things realized in real life and bang on these different tools. They are in their MVP stage, so there'll be all sorts of fun things to think about what we want to do next with and define that roadmap. The other thing that I think is maybe not obvious yet in talking just about the technology is that we have such a strong community of potential adopters.
KRISTEN RATAN: So we've been running these working groups and community calls and things with library publishers. And people are just-- they're showing up in large quantities. They're very excited. They're acknowledging that they are all on different timelines in terms of their own adoption-- ability to adopt, and what they're currently using. But there is a lot of interest in either participating in a pilot now or following along and looking at future pilots.
KRISTEN RATAN: Some of their requests have been, as we've known from the beginning of the project, that they'd like to see a pilot, for example, with OJS, which is a beloved platform for many and they want to see how that might work with some of these other components, like the web delivery platform or with the analytics dashboard or both. They're interested in experimentation with a range of IR softwares, including, for example, the new Haiku that's underway.
KRISTEN RATAN: So there's just a lot of excitement about how we can create that kind of diverse and lively ecosystem that combines open-source technologies with mission-aligned partners. And so, I think, watch this space because we will be launching future pilots that really expand this outwards. And with that, I will turn it over to Catherine Mitchell, who's going to talk about the CDL work that's underway and how that pilot is going to be proceeding.
CATHERINE MITCHELL: Thanks so much, Kristen. I'll start with a little bit of background on eScholarship for those of you who are unfamiliar with it. This year marks the 20th anniversary for eScholarship as an open access publisher. The program is run by the California Digital Library in collaboration with University of California campus library staff and provides open access publishing services for the 10 UC campuses, the Lawrence Berkeley Lab, and the UC Office of the President.
CATHERINE MITCHELL: As a library publisher, eScholarship is the home for 90 journals that claim an affiliation with the institution. That affiliation varies pretty dramatically, from journals that are flagship publications for campus-based research units, to undergraduate journals for first generation students in STEM, to international journals with maybe one UC faculty member somewhere on the editorial board.
CATHERINE MITCHELL: We have found a compelling niche for the library publisher in supporting emerging fields, interdisciplinary work, the work of underrepresented voices in scholarly communication, and any other kind of publication that either isn't well served by the commercial publishing marketplace or seeks an alternative to it. But eScholarship isn't just a publishing platform. It is also an open access repository, and as such provides access to over 300,000 research objects, from preprints to white papers to electronic theses and dissertations.
CATHERINE MITCHELL: It's also the repository where UC faculty continue to deposit tens of thousands of their publications under the UC open access policies. It's been important to us from the beginning of eScholarship to provide services for a broad range of scholarly output and to co-locate these items and provide unified access to them, regardless of type. We have a lot of different stakeholders at UC, from entire campuses, to departments, to multi-campus research units, each with different goals for their content and different notions of the kinds of collections they want to build within the system.
CATHERINE MITCHELL: EScholarship has faced some unique needs and challenges in working to provide access to this range of materials and range of expectations within a single platform. The metadata is inconsistent, yet we need a global search. The affiliations are often multiple for a single publication, and we need to display that publication everywhere that makes sense, while still maintaining a single version. The ambitions of our authors are vastly distinct, with some seeking to redesign scholarly communication altogether and others happy to stick with what they know but now in an open environment.
CATHERINE MITCHELL: We have attempted to use established platforms, but have found none that are well positioned to support this kind of complexity in a coordinated publisher plus IR role. We worked originally with the Berkeley Electronic Press to develop a combined publishing an IR platform, which later became B Press' Digital Commons product, but we eventually outgrew that as well. And as a result, we have found it necessary over the past two decades to build custom solutions to try to accommodate the complexities we face and provide a set of compelling publishing and distribution services to our academic community.
CATHERINE MITCHELL: The problem with custom solutions is that they are custom, and that means that when it comes to maintaining them, we're the only ones home. So while we have been in the business for years of providing just the kind of publishing plus IR solution that NGLP is working toward, the high level view of CDL's current architecture on this slide explains why we are absolutely thrilled to be piloting NGLP's tools and platforms.
CATHERINE MITCHELL: As you can see, all of our current systems are both idiosyncratic and out of date. This pilot is enabling us to engage more directly in community-led open-source platforms for our journal and IR workflows, where the work of maintaining and even advancing the systems is shared among a broad set of stakeholders. So in place of our custom IR framework and our long ago forked and now pretty much obsolete OJS instance, we will be using DSpace 7 and Janeway respectively.
CATHERINE MITCHELL: And in place of our custom web display platform and stat service, both of which take a significant toll on our technical team just to maintain and which lack some of the features are diverse group of stakeholders would like, we will be using state of the art solutions created within the NGLP project for aggregated display of content and analytics. We're excited to test run the NGLP web delivery platform because as described earlier, it isn't just a frontend display.
CATHERINE MITCHELL: It's a schema-driven system that has the flexibility and the robustness to avoid the kinds of genericizing compromises that we too often face in displaying a range of content this diverse. And we're also really looking forward to being able to track activity in the system, from the centralized analytics dashboard. Running 90 journals with a small staff is a tall order.
CATHERINE MITCHELL: Being able to proactively identify those publications and those research units that are flagging will give us an opportunity to intervene and provide assistance in a timely way. And our users can't wait for usage stats that render us something more than numbers on a spreadsheet. We will be running this pilot alongside our production system to test its ability to support the workflows and services that our large community of authors and researchers demand.
CATHERINE MITCHELL: We have high hopes for this set of solutions and are also excited to watch the system's extensibility unfold, making it easy to slot in other journal management systems, other IR platforms, and new systems that support new kinds of scholarly research outputs as they continue to emerge in this space. Now back to Kristen.
KRISTEN RATAN: Thanks, Catherine. It's so exciting that CDL is jumping in feet first on this and trying out basically everything that we're working on. And we'll get a lot of data and feedback on the CDL pilot alongside these other two. So just wrapping up here, as I mentioned, these pilots will be launching end of March, early April. We hope to launch a second round of pilots later in the year. PKP is really interested in doing a similar kind of assemblage, and we have a lot of other partners too, like For Science, who has expertise on DSpace.
KRISTEN RATAN: [INAUDIBLE],, for example, who's really interested in the analytics dashboard. There are really a lot of service providers out here, either that offer broad services or that are very niche, that are really excited that we've created this kind of modular package or suite. And as Catherine just said, it's an extensible and scalable suite.
KRISTEN RATAN: So we're acknowledging that we've only just really put a toe in the water with regard to existing open-source platforms that can be assembled and knitted together. And we're very interested in others who would like to partner with us on future pilots, people who may be interested in adopting one or more of these components, or create or adopt one of these service offerings.
KRISTEN RATAN: So contact us with information or questions about that. Also if you just want to dig in more deeply into what the technologies look like, we are developing out and in the open. We have open GitHub repositories as well as a kind of collection of documentation that you can see. If you are a library publisher or similar and want to join the user group and sort of follow along and attend meetings where you'll learn more about the future of each of these different components and the different service offerings, please do.
KRISTEN RATAN: We would love to have you and you'll be able to help shape the future of these. If you just want to get in touch and talk to us, that would be great. If you have other standards that you'd think we should be adopting, that is also something we want to hear from you on. And now, I'd just like to say we're really excited to hear from you right now about what your interests are and what your questions are, how we can leverage this sort of suite of solutions to make our content more discoverable and more machine-readable, compliant with best practices, as well as standards.
KRISTEN RATAN: So thanks very much.
TODD DIGBY: Well, thank you Kristen and Sarah and Catherine for such a great presentation on NGLP. Please join us now for the live portion of this session for further discussion and where we can have the opportunity to ask questions of our presenters. Thank you. [MUSIC PLAYING]
Segment:0 .
[MUSIC PLAYING]
TODD DIGBY: Welcome. My name is Todd Digby and I'll be the moderator of today's session. I'm the department chair of the Library Technology Services Department at the University of Florida. Today's presentation is titled "Centering interoperability in the future of library-based publishing." And as a look at the next generation library publishing project are NGLP. NGLP is a collaborative initiative of Educopia, California Digital Library, Strategies for Open Science, or Stratos, and the Confederation of Open Access Repositories, and is funded by Arcadia.
TODD DIGBY: Today, we are pleased to have Sarah Lippincott from Educopia, where she serves as the product owner of the Next Generation Library Publishing project; Kristen Ratan, the founder of Strategies of Open Science, or Stratos; and Catherine Mitchell, who is responsible for overseeing the strategic planning development and operational management of the California Digital Library's Publishing, Archives, and Digitization project. I will now turn it over to Sarah.
SARAH LIPPINCOTT: Thank you for having us, Todd. We're excited to talk to you about NGLP. I'm going to share my slides. As Todd mentioned, NGLP is a collaborative project. We have brought together stakeholders from Educopia Institute, the Confederation of Open Access Repositories, Stratos, the California Digital Library, to lead a project that is centered on values and principles that has values and principles at its core to develop software governance structures and service models to empower next generation library publishing.
SARAH LIPPINCOTT: So today, we're going to talk about our two interoperable standards-driven software components and the pilot implementations of those components that will bring our software-- our interoperable modular publishing stack-- to life. So a little bit of background on our project. Small, mission-driven digital first publishers, which include library publishers but also university presses or independent scholar-led presses, have a growing influence on scholarly communications, and they have over the last couple of decades.
SARAH LIPPINCOTT: The 2022 Library Publishing Directory, for example, counts 143 library publishers around the world actively publishing over 1,200 journals and who collectively issued over 1,600 monographs last year. These library publishers range from small liberal arts colleges, who are publishing maybe a handful of journals, to large universities and consortial initiatives building expansive portfolios of journals, books, learning objects, gray literature, experimental media, and other types of content.
SARAH LIPPINCOTT: Yet these publishers, despite the growing momentum and their growing influence, have had limited options when it comes to publishing technologies platforms and tools that meet their unique needs as library-based publishers. The NGLP's community engagement efforts over the past 18 months-- or two years, at this point-- have identified remarkably consistent needs, even across this very diverse field of different institutions and different contexts.
SARAH LIPPINCOTT: And NGLP emerged to address those needs. So we found that library publishers want to continue working with the familiar and functional open-source publishing tools that they already use. They don't want wholesale replacement of the publishing tools that work for them already. Rather, they want modular infrastructure that builds on top of what already is working. They want, however, a seamless, integrated user experience across these platforms, allowing for robust management and use of the entire diverse portfolio of library-published content.
SARAH LIPPINCOTT: In particular, library publishers told us that they see a need for unified web delivery that unites content from multiple sources. For example, a journal submission and review system and an institutional repository into a single, modern, flexible discovery and display platform. They want to continue to take advantage of the submission and curation tools that are optimized for different types of content, like OJS or Janeway for journals, and DSpace for institutional repository content like theses and dissertations, while also building a portfolio that reflects the full range of their scholarly and creative output.
SARAH LIPPINCOTT: Library publishers identified this platform, this kind of unified platform for display of journals and institutional repository content, as particularly mission critical. But the lack of available options for assembling this type of portfolio and managing this type of portfolio has led to two frustrations-- has led to library publishers feeling barriers to growth, and has also led to limited choice and vendor lock-in.
SARAH LIPPINCOTT: So the NGLP team believes that open-source software represents the best alignment between library publishers, their core values, their missions, and the way that they operate. But open-source software is really resource intensive to build and maintain. Many institutions, particularly small library publishers, lack the human or financial resources to implement open-source software.
SARAH LIPPINCOTT: So NGLP's goal is to make open-source software for publishing accessible to a range of institutional contexts and sizes by building not only these software components, but by developing a service provider network, a range of service models for providing a hosted and turnkey version of the NGLP publishing stack that is based around community, accountability, and trust, and that offers a la carte services that meet a range of different library use cases, and also allows institutions that do want to host software locally to do that as well and participate in a vibrant community of practice.
SARAH LIPPINCOTT: So now I'd like to ask Kristen to talk a little bit more about the way that we are building this community and how we will bring our code to life in the next phase of the project.
KRISTEN RATAN: Thanks, Sarah. That was a great introduction. When we started and embarked on this journey, which was now a couple of years ago, and kind of crafted what we thought this project needed to be we're really grateful for Arcadia to fund us to basically build a solution space. So when we began this process, we thought, what is it that the community really needs? The first thing one thinks of is, we need a new tool.
KRISTEN RATAN: We need a new platform. We need this one, single solution that will create all of the change and all the goodness that we think we need. In fact, when we embarked on this, we spent the entire first year of the 2 and 1/2 year project asking the community what they needed. And this was an excellent exercise because it moved us through this idea that there's some single solution out there to this idea that we need a really modular, interoperable set of solutions.
KRISTEN RATAN: What we needed to offer people was choice. And people were feeling very locked into things that they've made choices about in the past, and there wasn't a lot of flexibility and there wasn't a lot of ability to move from one thing to another. So we focused on choice. And what the library publishing community told us was there are a lot of things that are out there in the open-source world in publishing and in IR land that we are very happy with.
KRISTEN RATAN: These things should not be replaced. We don't want some new thing to come and sort of pave over all of the things that have been built before. What we want are-- we want any new development to fill specific gaps that we've identified, where there isn't a solution at the moment that's exactly what we want. But more than anything, they said, as Sarah alluded to, we need trusted service providers.
KRISTEN RATAN: We need service providers that also have those values and principles at their core and that will work with us to create sustainable solutions over time. Many libraries that are hosting their own open source are looking to move away from that. They're actually looking to outsource more than they had in the past. And those who are using outsourced solutions we're looking for values-driven ones and options there.
KRISTEN RATAN: So we consider this a problem space that needed a full solution space. And that's why the project has focused on everything from values and principles and what does it mean to be mission-aligned through what should the governance structures and business models look like between open source tools providers and service providers, how do you create that service layer as a full ecosystem.
KRISTEN RATAN: So you'll see we have a technology component, but that is by no means the only aspect of what we're doing. We're going to look at the technologies that NGLP has sponsored to be built. There are two in particular that are at the core of this and they're excellent pieces of technology. But we looked at how can they fit into this larger ecosystem. How can we make them interoperable with existing tools and platforms that people are using?
KRISTEN RATAN: We listened carefully to the library publishing community, who said in particular they're very happy, some of them with their OJS installation, or they're trying Janeway. Those are trusted, open-source platforms that they're using. There are any number of wonderful IR platforms, like DSpace, that they're using and they didn't necessarily want to make changes there. But we listened to what are the gaps that they needed filled, and then we'll talk about what those are.
KRISTEN RATAN: The second piece of this was that service layer. And so the way we've done that is we've talked to a number of service providers who work actively in this space-- and some of them we saw on the slide earlier-- and we said, can you step up and assemble a solution that includes technologies you've worked with in the past but also these new components that we're building? And it was amazing to see the response.
KRISTEN RATAN: Just like we'd gotten a really, really positive response from the library publishing community as we did the outreach, we had an equally enthusiastic response from potential service providers who were looking to meet a broader set of needs than they had done thus far. And so in light of that, we decided the best way to get them up and running was to set up pilots. And we are launching with three pilots coming up shortly, and we'll talk a little bit about that in a minute.
KRISTEN RATAN: But in addition, we see this as a way of making continual improvement all along the way. So new pilots will be launching after that, with people who are maybe interested in creating a different assembled solution or meeting a different market need. So that kind of flexibility is, we feel, essential to be able to create sustainable service models moving forward.
KRISTEN RATAN: Sarah.
SARAH LIPPINCOTT: Thanks, Kristen. So I'm going to talk to you more about the specific components that we're building. The NGLP team is partnering with Cottage Labs and Cast Iron Coding, two really amazing development partners who are building two open-source software components that will be licensed under an MIT license and available for anyone in the community to adopt, including the pilot service providers that we are bringing on as part of NGLP project to test out both the technology and service delivery.
SARAH LIPPINCOTT: So the first component that we are building is a web delivery platform for unified content discovery and display, which is based on the specific feedback that I mentioned, that Kristen mentioned as well, that library publishers want us to take modular components-- take components that they already use in their workflow and knit those together into an end to end platform that meets their needs for library publishing. The web delivery platform is designed to support multiple upstream submission systems, such as Janeway, OJS, and DSpace, aggregate content from them into a unified discovery and display platform, and allow administrators to mix and match content into different collections, customized templates for different community pages, and all while supporting a single public-facing access point to the rich portfolio of content that they're assembling.
SARAH LIPPINCOTT: So you can see here that you can have journals running through Janeway or OJS, for example, and we'll be demonstrating this workflow in one of our pilots led by Janeway to submit articles through Janeway and have them appear in the web delivery platform as the front end, and combine it with content that comes out of an institutional repository platform, like DSpace, into a single, unified portfolio.
SARAH LIPPINCOTT: This was something that was identified as extremely important to our library publishing community and they wanted something that allowed them to be flexible, to evolve over time, and to continue to work with the tools that they're already using. We want this software component to be flexible, content-agnostic, work for a range of scales and contexts of library publishing, and we wanted it to rely on standards and structured data to ensure machine readability, data portability in the future, and interoperability with these upstream systems.
SARAH LIPPINCOTT: So the data structures in the web delivery platform, to that end, are not hard-coded, but are defined by JSON schemas. This provides a lot of flexibility for the platform while also ensuring that content is machine-readable and portable. The web delivery platforms API-based front end, which I'll demonstrate for you in a moment, is powered by-- provides access to and is a first class consumer of a machine-readable-- sorry, a GraphQL API, which allows the web delivery platform itself and other applications to query and mutate the stored data.
SARAH LIPPINCOTT: And because the web delivery platform is a first class consumer of its API, it's built upon a framework of structured data. The structure can evolve over time and the front end can be modified-- frontend templates can be modified to accommodate new data points, new views of data, so it can support an evolving array of content. And configurable content schemas defined in JSON allow the WDP to move from generic entities into recognizable types of content, so moving from collections and items defined in the abstract, to journals, articles, books, and build metadata schemas that are appropriate for different content types.
SARAH LIPPINCOTT: So these schemas not only govern content but also components on a page display within different templates so that you have appropriate context for a range of different content types, whether that's IR-type content, theses and dissertations, or whether it's journals, that you have templates that make sense for the type of content you're displaying, and you can have disparate content types unified in a single system that are searchable side by side, but displayed in templates optimized for their content.
SARAH LIPPINCOTT: So what we've developed is not just a front-end display, but really a publishing framework that's content-agnostic and scalable. Closely coupling presentation to the content schemas also allows the web delivery platform to avoid the kind of generic rendering and UX that kind of characterizes a lot of institutional repository software. And in future iterations of the WDP, we hope to include interfaces that will allow developers to package these presentational components and metadata schemas as reasonable or adoptable plugins that could be shared between institutions.
SARAH LIPPINCOTT: So by developing these schemas, by developing this kind of publishing framework, we're also seeding a community of practice around the web delivery platform, where you can have communities sharing their own contributions back to the software. We're also providing built-in support for controlled vocabularies for taxonomies like credit, for example, incorporating persistent identifiers, ensuring we have DOIs and ORCIDs being a core part of how data is stored and displayed.
SARAH LIPPINCOTT: And we envision a lot of exciting possibilities in the future as the software develops for integration with services like ORCID. And we're relying on standards to pull in information into the web delivery platform. So we are using OAIPMH to pull in metadata and content from all of the systems into the web delivery platform. So we're pulling in metadata in standard formats from an OAIPMH feed, and we're also able to pull in JATS full text, where it's available, from systems like Janeway so that we can have the dynamic-- so that we can have HTML display of full text where it's available, which is something that is an aspiration for a lot of library publishers to begin investing more in HTML display and moving a little bit away from PDFs.
SARAH LIPPINCOTT: So I'm going to do a new-- I'm going to share my screen and give you a look at the web delivery platform. So as you can see, the web delivery platform allows multiple communities to exist side by side, communities being the kind of top level collection in our schema. This use case is something that Kathryn Mitchell will describe further, that is ideal for library consortia, for example, to have different partners or different stakeholders having their own kind of space within a single instance of the web delivery platform.
SARAH LIPPINCOTT: But it's also a way that any library publisher can create these kind of top level collections. We're going to take a deeper dive into one of these collections. You can see we get a few nice stats right off the-- right on the front page to give a sense of how lively and vibrant these different communities are. Each community has its own dedicated landing page that can have its own logo and imagery to give it its own look and feel.
SARAH LIPPINCOTT: In the future, we plan to offer more customizations to these community templates so that different communities could really differentiate themselves from one another and have more variety and more choice for different communities to customize things like colors and fonts. Communities can choose content to highlight on the home page. Here we have a number of journals, one of which has a cover image that was uploaded and the rest have cover images that were actually generated algorithmically within the web delivery platform.
SARAH LIPPINCOTT: So you get nice imagery even if you don't have a-- If you don't have somebody selecting a cover image for everything, the system will generate one for you. And we'll take a look at one of these example journals. So we're drilling down through content here. So each journal landing page, again, can be customized. So this is-- let's actually go back to the journal content.
SARAH LIPPINCOTT: So you can see, this one has been filled out with more metadata. We can see how it's licensed, whether the articles are peer-reviewed, other important metadata right up there at the top. We can have a hero image in these templates. There's a wide range of customizations that we can make to any kind of journal page. And again, all of this is powered by those schemas, so it's very flexible and dynamic, and these templates can change and evolve over time, as needed.
SARAH LIPPINCOTT: And content can be presented in different ways. So we can have content from the current issue automatically highlighted on this journal landing page. We can also browse all issues of a journal. We can browse related journals. We can browse all of the articles. So all of this content is very flexible, can be mixed and matched and presented in a range of different ways. On an article page, we have the ability to post full text HTML when it's available alongside metadata information about contributors, which are their own entities.
SARAH LIPPINCOTT: So if we click on a contributor, we can see all of that author's publications, again, generated from-- dynamically populated. And we have a placeholder here for embedded metrics, which will be coming from the second component, which I'll describe in just a moment.
SARAH LIPPINCOTT: And finally, we can use this picker up here to select different communities and kind of navigate through different areas of the web delivery platform. We're currently working on Search as well, so we'll have cross-platform discovery, again, facilitating the ability to have communities that have primarily journal content and IR content living side by side, giving all of that content excellent discoverability, really polished, modern presentation that puts all of this content, really showcases it, and puts it on equal footing.
SARAH LIPPINCOTT: And finally, I'm going to share the NGLP's other component being developed by our partners at Cottage Labs, which is an analytics dashboard. So going along with our web delivery and display of content, our community told us that they really needed robust metrics that would give them insight into and oversight of managing this content portfolio.
SARAH LIPPINCOTT: They need insight into how publications are moving through the system before they are published, and then they need post-publication engagement and readership metrics. So the analytics dashboard uses-- I've lost my window with slides.
KRISTEN RATAN: While you're looking for that, Sarah, I'll just mention that what's exciting about the analytics dashboard is the ability to pull analytics from multiple platforms, existing platforms like OJS or Janeway or DSpace, as well as the new web delivery platform, and being able to unify those in a single place, which has been a struggle, frankly, in publishing for a long time. So this is a really exciting solution and it's a standalone solution that could be applied to anybody else's platforms out there.
SARAH LIPPINCOTT: Absolutely. So just to give an image to what Kristen is mentioning, so we are aggregating workflow metrics. Much in the same way that the web delivery platform is aggregating content from these upstream systems, we're aggregating workflow event data with usage event data into a series of dashboards that are customized for different stakeholder groups.
SARAH LIPPINCOTT: The dashboard uses a custom JavaScript framework developed by Cottage Labs to generate these dynamic visualizations. And for the RMVP release, the dashboard is capable of harvesting data from Janeway and from the web delivery platform, but we intend for it to be able to harvest data from multiple upstream systems. And a data archive that underlies all of this allows administrators to go back to the raw data as it's harvested, before it's normalized for presentation in the dashboard, ensuring that there's access to data in case of any questions about integrity.
SARAH LIPPINCOTT: And we want all of these metrics to be traceable and transparent. Our metrics are not currently counter compliant, but we aspire to provide robust and very granular metrics that stakeholders can drill down into, can build their own reports, ultimately, and can export data in multiple formats for further analysis as well.
SARAH LIPPINCOTT: This report shows engagement metrics. So this is post-publication engagement. We're pulling in data, in this case, from the web delivery platform. You could envision pulling in event data, usage data, from multiple systems, but our primary consumer for the post-publication metadata for our pilots will be the web delivery platform itself.
SARAH LIPPINCOTT: And this dashboard allows all of the-- provides all the capabilities that library publishers want, that you kind of expect from an analytics dashboard-- the ability to filter or to limit by a time range, by different types of interactions, by different content formats within the repository. We provide a map of engagement geographically, and the map also serves as a navigation mechanism.
SARAH LIPPINCOTT: So as you zoom in on the map, these graphs adjust dynamically so that you can see more specific information related to how content is being engaged with in different parts of the world. And we can see our download formats in an interactive bar graph down here as well. So this is the engagement report. We've also-- or engagement dashboard.
SARAH LIPPINCOTT: We've also built a dashboard for workflow metrics. I want to leave time for us to talk a little bit more in-depth about the pilot implementations of these software, so I'm not going to demonstrate that one at this point. But we are really proud of the work that both of our development partners have done, that has been deeply informed by our community engagement work that we've continued throughout the development process, and we're really excited to put these to the test during our pilot implementations.
SARAH LIPPINCOTT: So Kristen, can you give us a little bit of-- can you start us off talking a little bit about how we'll bring these to life over the next few months?
KRISTEN RATAN: Absolutely. And I do want to-- shout out to Cast Iron Coding and Cottage Labs, who have been our technology partners. It has been a pleasure working with highly competent, very highly motivated, and very creative partners, both of them. And they've each brought different things to the table. But one thing that both of these dev shops have demonstrated is a commitment to using standards and commonly used tools, softwares, et cetera, the whole way through.
KRISTEN RATAN: So this is important in library publishing, where things have not always been up to the kind of publishing standards that many of us are used to. And so now we are able to offer software solutions and services that give all the content DOIs, for example, or can collect ORCIDs, or can show counter compliance statistics that utilize OAIPMH and be able to contribute back to those standards as well.
KRISTEN RATAN: So this is a really exciting way to move forward. And the pilots that we are launching are really the demonstration cases for this. So this is sort of where the rubber hits the road. We get to the exciting part. We want to show that we have scalable solutions and we're testing real world implementations. So we have three pilots that assemble these modules into the end to end services that people need, and we're working both with technology and service partners to make this happen.
KRISTEN RATAN: And it gets a little confusing because sometimes the technology partner is also a service partner. So other use cases in content types are on the roadmap, but for the moment, we're starting with what the community told us they wanted the most, which was a combination of IR and journals, or journal-only solutions. So people have a lot of ways to do IRs only. This idea was really about how do you help those libraries that are also publishing journals, and then eventually things like books and OER?
KRISTEN RATAN: So this is our starting point. We have three pilots. The first one is demonstrating what a sort of turnkey hosted journal plus IR solution would look like, that builds on this particular one, uses Janeway as its manuscript submission system, a headless Janeway. A content then flows into the WDP so that it can meet up with IR content that may have come, from example, from DSpace or other IRs, and be displayed alongside-- so journal and IR content can be displayed together in the web delivery platform and then the analytics dashboard is able to pull analytics from both the manuscript submission Janewayside, as well as the web delivery platform side.
KRISTEN RATAN: So this is a unified IR plus journal solution that was really one of the leading requests that came out of our community engagement. So we're super excited about that. The second is a CDL-run pilot. So CDL has always been, from the beginning of this project, an exemplar for us as a way that library publishing can combine various content types and have that unified display that you see on eScholarship, CDL's platform.
KRISTEN RATAN: In CDL, as one of the key partners here-- and Catherine is one of co-PIs-- was very eager to say, OK, how can we improve our own digital library, essentially, and how can we use these open source components and be able to combine them and create interoperability within our own implementation? So CDL is testing these modules, which has been fantastic. CDL is testing, for example, the DSpace to WDP flow, which is great; and how the analytics dashboard will work, whether a WDP can be swapped in for what they're currently using.
KRISTEN RATAN: And then the third is a journals-only pilot. So this meets the use case of when somebody's got other needs met elsewhere, but they really need a new, modern, well-functioning, hosted journal system that really can rival what other journals are doing out there. And so this one is being run by Longleaf Services, which is a non-profit subsidiary of the UNC Press. And they'll be working with the campuses there in the UNC system.
KRISTEN RATAN: And they're running Janeway as their manuscript submission system and the web delivery platform as their display layer, with the analytics dashboard being able to pull from both. So those are the three-- and they have-- as I mentioned, they have constituents within the UN system that are eager to jump in and do this trial. Janeway for that pilot, the journal plus IR. We have a number of library publishers very eager to participate.
KRISTEN RATAN: And I think we'll probably have about five. We'll be launching these pilots at the end of March, first week of April time frame. And we'll be able to run them as real experiments. We have acceptance criteria lined up. The pilot partners will test and try this with their own content, with their own data, and be able to give us really detailed feedback. The pilots will run a few months, and then we'll have a report out on how things have gone.
KRISTEN RATAN: So this is really exciting because it's really the fun part, where we get to see things realized in real life and bang on these different tools. They are in their MVP stage, so there'll be all sorts of fun things to think about what we want to do next with and define that roadmap. The other thing that I think is maybe not obvious yet in talking just about the technology is that we have such a strong community of potential adopters.
KRISTEN RATAN: So we've been running these working groups and community calls and things with library publishers. And people are just-- they're showing up in large quantities. They're very excited. They're acknowledging that they are all on different timelines in terms of their own adoption-- ability to adopt, and what they're currently using. But there is a lot of interest in either participating in a pilot now or following along and looking at future pilots.
KRISTEN RATAN: Some of their requests have been, as we've known from the beginning of the project, that they'd like to see a pilot, for example, with OJS, which is a beloved platform for many and they want to see how that might work with some of these other components, like the web delivery platform or with the analytics dashboard or both. They're interested in experimentation with a range of IR softwares, including, for example, the new Haiku that's underway.
KRISTEN RATAN: So there's just a lot of excitement about how we can create that kind of diverse and lively ecosystem that combines open-source technologies with mission-aligned partners. And so, I think, watch this space because we will be launching future pilots that really expand this outwards. And with that, I will turn it over to Catherine Mitchell, who's going to talk about the CDL work that's underway and how that pilot is going to be proceeding.
CATHERINE MITCHELL: Thanks so much, Kristen. I'll start with a little bit of background on eScholarship for those of you who are unfamiliar with it. This year marks the 20th anniversary for eScholarship as an open access publisher. The program is run by the California Digital Library in collaboration with University of California campus library staff and provides open access publishing services for the 10 UC campuses, the Lawrence Berkeley Lab, and the UC Office of the President.
CATHERINE MITCHELL: As a library publisher, eScholarship is the home for 90 journals that claim an affiliation with the institution. That affiliation varies pretty dramatically, from journals that are flagship publications for campus-based research units, to undergraduate journals for first generation students in STEM, to international journals with maybe one UC faculty member somewhere on the editorial board.
CATHERINE MITCHELL: We have found a compelling niche for the library publisher in supporting emerging fields, interdisciplinary work, the work of underrepresented voices in scholarly communication, and any other kind of publication that either isn't well served by the commercial publishing marketplace or seeks an alternative to it. But eScholarship isn't just a publishing platform. It is also an open access repository, and as such provides access to over 300,000 research objects, from preprints to white papers to electronic theses and dissertations.
CATHERINE MITCHELL: It's also the repository where UC faculty continue to deposit tens of thousands of their publications under the UC open access policies. It's been important to us from the beginning of eScholarship to provide services for a broad range of scholarly output and to co-locate these items and provide unified access to them, regardless of type. We have a lot of different stakeholders at UC, from entire campuses, to departments, to multi-campus research units, each with different goals for their content and different notions of the kinds of collections they want to build within the system.
CATHERINE MITCHELL: EScholarship has faced some unique needs and challenges in working to provide access to this range of materials and range of expectations within a single platform. The metadata is inconsistent, yet we need a global search. The affiliations are often multiple for a single publication, and we need to display that publication everywhere that makes sense, while still maintaining a single version. The ambitions of our authors are vastly distinct, with some seeking to redesign scholarly communication altogether and others happy to stick with what they know but now in an open environment.
CATHERINE MITCHELL: We have attempted to use established platforms, but have found none that are well positioned to support this kind of complexity in a coordinated publisher plus IR role. We worked originally with the Berkeley Electronic Press to develop a combined publishing an IR platform, which later became B Press' Digital Commons product, but we eventually outgrew that as well. And as a result, we have found it necessary over the past two decades to build custom solutions to try to accommodate the complexities we face and provide a set of compelling publishing and distribution services to our academic community.
CATHERINE MITCHELL: The problem with custom solutions is that they are custom, and that means that when it comes to maintaining them, we're the only ones home. So while we have been in the business for years of providing just the kind of publishing plus IR solution that NGLP is working toward, the high level view of CDL's current architecture on this slide explains why we are absolutely thrilled to be piloting NGLP's tools and platforms.
CATHERINE MITCHELL: As you can see, all of our current systems are both idiosyncratic and out of date. This pilot is enabling us to engage more directly in community-led open-source platforms for our journal and IR workflows, where the work of maintaining and even advancing the systems is shared among a broad set of stakeholders. So in place of our custom IR framework and our long ago forked and now pretty much obsolete OJS instance, we will be using DSpace 7 and Janeway respectively.
CATHERINE MITCHELL: And in place of our custom web display platform and stat service, both of which take a significant toll on our technical team just to maintain and which lack some of the features are diverse group of stakeholders would like, we will be using state of the art solutions created within the NGLP project for aggregated display of content and analytics. We're excited to test run the NGLP web delivery platform because as described earlier, it isn't just a frontend display.
CATHERINE MITCHELL: It's a schema-driven system that has the flexibility and the robustness to avoid the kinds of genericizing compromises that we too often face in displaying a range of content this diverse. And we're also really looking forward to being able to track activity in the system, from the centralized analytics dashboard. Running 90 journals with a small staff is a tall order.
CATHERINE MITCHELL: Being able to proactively identify those publications and those research units that are flagging will give us an opportunity to intervene and provide assistance in a timely way. And our users can't wait for usage stats that render us something more than numbers on a spreadsheet. We will be running this pilot alongside our production system to test its ability to support the workflows and services that our large community of authors and researchers demand.
CATHERINE MITCHELL: We have high hopes for this set of solutions and are also excited to watch the system's extensibility unfold, making it easy to slot in other journal management systems, other IR platforms, and new systems that support new kinds of scholarly research outputs as they continue to emerge in this space. Now back to Kristen.
KRISTEN RATAN: Thanks, Catherine. It's so exciting that CDL is jumping in feet first on this and trying out basically everything that we're working on. And we'll get a lot of data and feedback on the CDL pilot alongside these other two. So just wrapping up here, as I mentioned, these pilots will be launching end of March, early April. We hope to launch a second round of pilots later in the year. PKP is really interested in doing a similar kind of assemblage, and we have a lot of other partners too, like For Science, who has expertise on DSpace.
KRISTEN RATAN: [INAUDIBLE],, for example, who's really interested in the analytics dashboard. There are really a lot of service providers out here, either that offer broad services or that are very niche, that are really excited that we've created this kind of modular package or suite. And as Catherine just said, it's an extensible and scalable suite.
KRISTEN RATAN: So we're acknowledging that we've only just really put a toe in the water with regard to existing open-source platforms that can be assembled and knitted together. And we're very interested in others who would like to partner with us on future pilots, people who may be interested in adopting one or more of these components, or create or adopt one of these service offerings.
KRISTEN RATAN: So contact us with information or questions about that. Also if you just want to dig in more deeply into what the technologies look like, we are developing out and in the open. We have open GitHub repositories as well as a kind of collection of documentation that you can see. If you are a library publisher or similar and want to join the user group and sort of follow along and attend meetings where you'll learn more about the future of each of these different components and the different service offerings, please do.
KRISTEN RATAN: We would love to have you and you'll be able to help shape the future of these. If you just want to get in touch and talk to us, that would be great. If you have other standards that you'd think we should be adopting, that is also something we want to hear from you on. And now, I'd just like to say we're really excited to hear from you right now about what your interests are and what your questions are, how we can leverage this sort of suite of solutions to make our content more discoverable and more machine-readable, compliant with best practices, as well as standards.
KRISTEN RATAN: So thanks very much.
TODD DIGBY: Well, thank you Kristen and Sarah and Catherine for such a great presentation on NGLP. Please join us now for the live portion of this session for further discussion and where we can have the opportunity to ask questions of our presenters. Thank you. [MUSIC PLAYING]
Form Title Download
Video
Transcript
Form Title Bookmark
Entire Media
Segment(s)
Custom Clip
Start At:
End At:
Form Title Share
Entire Media
Segment(s)
Custom Clip
Start At:
End At:
Form Title Accessibility and Keyboard Shortcuts
The cadmore media player is a professional video and audio player experience designed to deliver media as well as relevant transcript, segmentation, and metadata. On the screen is a traditional html video player with buttons such as play, pause, forward, captioning, language and play speed selection and more. Adjacent to the video player are generally tabs, one of which shows a scrolling transcript of the video and the other shows any segmentation of the media, sometimes referred to as chapters. At the top of the video is a menu bar containing an Explore button and Tools button. The Explore button allows you to dig deeper into the video by opening up an explore dialog which contains tabs for a visual navigation of the video using thumbnails, an about tab which contains rich metadata about the media, a segments tab which contains further information about the video, and a related tab which contains links to other media related to this media. The tools button opens a menu with options for sharing the media on social media, creating bookmarking links, creating embed codes for your website, generating citations, and more.
Keyboard Shortcuts
Keyboard shortcuts only work while you are in forms mode. By entering forms mode, you will be able to quickly access portions of the media player with single key commands.
Spacebar: Play/Pause Toggle
I: Info Menu,
O: Tools Menu
T: Transcript Tab,
S: Segments Tab
F: Forward 15,
R: Rewind 15
L: Languages,
P: Playspeed
M: Mute Toggle,
V: Volume Bar
N: Video Only Toggle,
B: Full Screen Toggle
C: Captions Toggle
Escape: Closes dialogs and menus / Exits Player
Z: Next Transcript Chapter
X: Previous Transcript Chapter
Q: Next Transcript Paragraph
W: Previous Transcript Paragraph
Entire Media
Segment(s)
Custom Clip
Start At:
End At:
Embed Size
-
You Size - Responsive
-
We Size - Responsive
-
Picture Overlay Popup
-
400 x 225
-
512 x 288
-
400 x 700
-
768 x 1024
-
1024 x 512
-
1280 x 608
Form Title Cite
No citation provided.
Info
Segments
Related
Thumbnails
Exit Clip Mode
You have requested to see a portion of the video outside of the clip.
Click OK to switch to the full video or click if you would like to stay inside the clip. You can always go back to the clip with Tools and Clip Mode