Name:
Composing for the non-text infrastructure dance-NISO Plus
Description:
Composing for the non-text infrastructure dance-NISO Plus
Thumbnail URL:
https://cadmoremediastorage.blob.core.windows.net/4a9f1df6-8414-410e-9503-de95db6181c3/thumbnails/4a9f1df6-8414-410e-9503-de95db6181c3.png?sv=2019-02-02&sr=c&sig=1vo6QakU%2Fo2lGKyHXVXFLJFQKLxnuHAunb2WhhDO2Zk%3D&st=2024-12-27T04%3A19%3A10Z&se=2024-12-27T08%3A24%3A10Z&sp=r
Duration:
T00H43M47S
Embed URL:
https://stream.cadmore.media/player/4a9f1df6-8414-410e-9503-de95db6181c3
Content URL:
https://cadmoreoriginalmedia.blob.core.windows.net/4a9f1df6-8414-410e-9503-de95db6181c3/Composing for the non-text infrastructure dance-NISO Plus.mp4?sv=2019-02-02&sr=c&sig=eUC20f2lkRhNrPv%2F6fb7qg9L9LcszFb0PQzHBpfrRjE%3D&st=2024-12-27T04%3A19%3A11Z&se=2024-12-27T06%3A24%3A11Z&sp=r
Upload Date:
2022-08-26T00:00:00.0000000
Transcript:
Language: EN.
Segment:0 .
[MUSIC PLAYING]
SPEAKER 1: Welcome to our session. I'll hand it off to Jenny.
JENNY EVANS: OK. Thank you very much, Kelly. Hopefully, you can all hear me. My name is Jenny Evans. I'm research environment and scholarly communications lead at the University of Westminster based in London in the UK. And I'll be kicking off our session today, composing for the nontext infrastructure dance. And my colleagues will introduce themselves as they take over the mic.
JENNY EVANS: In today's session, we're talking about identifying challenges facing scholarly communities whose main method of communication is not the written article, but it's some other form of output. How do we ensure that rich metadata functionality narratives built into institutional and other platforms can expose and transmit information to the wider academy registries and enable discovery access and inquiry without losing detail?
JENNY EVANS: We'll be talking more about that throughout this presentation. What we want you to think about as we speak today-- for these non-textual outputs, do we need to change or create technologies or capture practice and build solutions around use cases? Do we understand enough about what we need? Where do the responsibilities and the power structures lie between the various stakeholders for addressing complex issues affecting core research infrastructure?
JENNY EVANS: And how do we reach community agreements on taxonomies and other key exchange or interoperability mechanisms? And why are we speaking today and what are we are speaking about? We going to give you some definitions about practice research and other in context of practice research. The background of the work we've been doing as a group and as a project.
JENNY EVANS: Over the past three years, we will use two main case studies at the University of Westminster and then the British Library. We've got a raft of information and ideas and thoughts about metadata and persistent identifiers and its environments. And finally, we'll talk a bit about our recently AHRC-- Arts and Humanities Research Council-- funded project Practice Research Voices or PR Voices and how we want to change the world in collaboration with all of you here today.
JENNY EVANS: So what do we mean by other in the context of practice research? There's lots of conversations already going on in this area around things like computer programming, outputs and standards, other kinds of ideas. However, what we're talking today is about artifacts, competitions, designs, digital visual media, exhibitions and performance. So when we're talking about practice research at the moment, we're very much focusing on practice research in the arts and architecture, so that more creative community.
JENNY EVANS: And just some definitions, as people on this call or presentation today might not be so familiar with these definitions. So practice research is an umbrella term that describes all manners of research where the practices the methods of research conveyed in a research output. So it can cross disciplines. It's very interdisciplinary.
JENNY EVANS: It's not just about arts and architecture. However, that's our experience thus far, which have distinct and unique balances of practice research narrative complementary methods within their projects. This idea of research narrative is really important. This research tends to be multi-component, so it's not an individual research output like, for example, journal article or book chapter. So in our practice, research output and narrative may be conjoined-- it often is-- or embodied in practice.
JENNY EVANS: And that research narrative articulates that research inquiry that emerges in the practice. Now, these definitions are from a report that we'll refer to today as one of the PRAG UK reports. And the first one is the "Practice Research-- What is practice research?" The second one is "How practice research can be shared." These reports were commissioned by the practice research advisory group based in the UK and funded by a variety of UK universities and funders.
JENNY EVANS: And they were authored by James Bullion, Ozden Sahin at Goldsmiths University. The second PRAG-UK report 2, which really underpins a lot of what we'll be talking about today, focuses on how can practice research be shared. One of the recommendations of the report is investigating the founding of an Open Library of Practice Research which would harvest and host peer reviewed practice research outputs, provide specific support and embodying principles of open access.
JENNY EVANS: I think that's really kind of key underlying part of our presentation today is about open standards. And how do we work with existing standards and update them and improve them, rather than creating many new standards? Recommendations of the second report looked at the structuring of practice research, item types, formats and metadata, peer review-- which we won't be covering in the project or in our presentation today-- storing and preserving these outputs and sharing these outputs.
JENNY EVANS: So if you're interested in finding more out about the two reports, you can go away and read those. So how did Rachael, Adam and I get to be here today? So it's been a three year journey, 3 and 1/2 year journey for me at any rate, that started the Repository Fringe in Edinburgh in 2018. I'll talk a bit about our journey at the University of Westminster, but there's been a variety of conversations in very different communities.
JENNY EVANS: And that's been one real learning piece for all of us, is that there are many different communities talking about practice research. So as you can see, a repository fringe. There's been discipline focused events, so PRAG-UK events. There's been [INAUDIBLE] events. We ran a panel session, Open Repositories, back in 2019 in those days where you had in-person conferences. It was certainly my baptism of fire to open repositories with the presentation of panel session 24/7 presentation and a poster.
JENNY EVANS: The regional meeting in March 2020 picked it up. There was a research data management event run by the DCC. Research excellence framework is the UK's regular reporting. Every 8 or 9 years, we report to our recent major research funders, UK research and innovation, about our research activities and outputs. Practice for research is a key element of their outputs submission.
JENNY EVANS: The PRAG reports were published in July last year. There was a digital research community events on practice research. The UK reproducibility network event on it. And then we spoke at the aimos conference late last year and FORCE11 as well. So just picking up briefly, which we'll come back again and again today, is this idea of reproducibility.
JENNY EVANS: So reproducibility is obviously a key core component of open research and open research infrastructures. And everything we talk about today really aims partly towards making this research reproducible. So it can be shared. It can be considered. It can be reused and reproduced in the same way that science technology, engineering and medicine or text based outputs can be shared.
JENNY EVANS: So this particular, I think, coalition of voices started in PIDapalooza in January 2021 based on the work we've done. Haplo and Cayuse [INAUDIBLE] repository [INAUDIBLE] one repository solution that I'll speak about. And Jessica been doing to capture more effectively practice research. And that was followed up partly at aimos, an Australian [INAUDIBLE] conference, and then the FORCE11 conference last year where we started actually articulating and illustrating the unfairness of that discoverability landscape for practice research.
JENNY EVANS: And really, a real focus for me personally and for us as a group is around how we make this landscape fairer and how this research becomes on a par and recognized as our journal, articles, book chapters and other text based outputs. So what have we been doing at University Westminster? Now, apologies. We have actually blurred out this image on purpose. Just as a very brief aside.
JENNY EVANS: I said I'd try not to mention the research excellence framework or our portfolios that go into Ref. Our creative arts college or school have gone into [? RefWorks ?] and that's how we've built that's what we focused on our work on at Westminster. And because this research is evaluated by our funder, it leads to funding. We're very slowly releasing the public access versions of these portfolios, but this one is actually [INAUDIBLE] Bass Culture project that actually there's some work going on with British Library about it.
JENNY EVANS: So what have we done at Westminster? So we work with Haplo, now a division of Cayuse, a US company, to build a single open-source bare repository to capture all research enabled by this flexible technology. This really mattered. I very much see practice research as a real combination of open access and data sharing. Because we're talking not just about single outputs, but we're talking about a collection of files, images, and text outputs.
JENNY EVANS: We've been very lucky. We've got very collaborative arts and architecture practice research community, and we've worked very closely with them. We've also very much been informed by previous and existing work. There were a number of Jisc-funded projects in the UK, probably about 10 years ago now. Capture Culture, Cultivate, I think that's a few of them. So they've done a lot of work with the e-print software.
JENNY EVANS: We've also looked very closely at the Journal of Artistic Research and the Research Repository, which are European-based art practice research infrastructures. Our institutional policy landscape recognizes this research, even if the external policy landscape doesn't. This is a really key point. So these researchers don't get recognized and get benefit of open-access funding, for example.
JENNY EVANS: And depending on whether or not they're in a university, they might not even get funding, even if they are in a university. And just the general infrastructure funding tends to support those more STEM, text-based research. Challenges we've identified, the persistent identifier metadata landscape doesn't really work for this research. And I think the danger of that is that these communities will look elsewhere.
JENNY EVANS: They'll go and find other ways of making their research discoverable if we don't step in and do this and do this in a very open way so that it makes the most of open infrastructures. I think copyright and licensing issues are a challenge for our university particularly. Our scholarly works are covered as copyrights for our researchers. So again, regular journal articles, books, book chapters.
JENNY EVANS: As soon as you start talking about videos, artifacts, objects, exhibitions, you've got to deal with it one-by-one. This community are also less used to reusing or enabling the reuse of their content, so licensing is not something that's thought about. So what we discovered is this landscape is quite unfair, and this isn't to blame scientific communication and that network. It's more just to explain where it's at.
JENNY EVANS: So practice-based arts research. What we able to do, thanks to our flexible repository technology, is update item type, the practice research arts item type. We introduced a new exhibition type, and we introduced the idea of a dynamic portfolio or collection. So that has really enable us to reflect how these researchers see their research, which sounds a bit silly.
JENNY EVANS: But I think scientists are much more attuned to, well, I published a journal article that looks like this. Whereas these researchers, the way you see their research on a web page and they do often quite often use websites to capture their research, which has a whole load of digital preservation issues assigned around that. What it looks like matters.
JENNY EVANS: So on the right, we've got an example of our previous open-access repository. And then on the bottom, we've got the newly-released Westminster research. There's just much, much more flexibility in how it looks. So we could improve the display, the accessibility regulations, and SEO have built into the repository pages. So they're much more discoverable. However, as Rachael and Adam will be speaking about later in this presentation, that doesn't necessarily mean it's anywhere near fair in terms of how you find this research.
JENNY EVANS: And because of the flexibility of the technology, we had an iterative development cycle. So we went through a couple of iterations over a good couple of years to get where we are now. So this is a lot of detail. But hopefully, you can see it as you'll be watching this from home or from your screen somewhere. So just an example of what we were able to do with our flexible templates.
JENNY EVANS: So you'll see, on the left, the exhibition type, where we've got to-- oh, I've managed to scroll on there. Title of work was important rather than just title. We've called this "creator." We've been able to acknowledge the collaborative role that this research community value with product description rather than abstract. The media type is now a subcategory within each template rather than it being an output type in its own right.
JENNY EVANS: We've added the exhibition title. Commissioning body was really relevant to our architecture researchers. And on the right, we've got the latest iteration of what we called our own "enhanced portfolio template." And I think what it's really-- like, again, there's a lot of detail here. But what sort of like-- I keep clicking through the next slide.
JENNY EVANS: Apologies. Is that we've got different tabs in this particular output type. We've got multiple files. And again, when we're talking about SEO and discoverability, that can be an issue. We've got different license types. We've got a combination of open and closed access files. And really, just a much more complex output type, which the Research Excellence Framework tends to call a "multi-component output type," which I think is a really good definition.
JENNY EVANS: So that's where I will leave you, so that's sort of our journey at Westminster so far. I'm now going to hand over to Rachael, who will be speaking about The British Library's experience.
RACHAEL KOTARSKI: Thank you very much, Jenny. Yes, I'm Rachael Kotarski. I am from The British Library, which is the national library of the United Kingdom for those who aren't familiar with us. We have a statutory remit in supporting research across all disciplines and in all forms, but we don't just support direct to researchers who walk through our doors or happen upon our website. We also look at how we support research with research infrastructure, and that's where my role comes in and the head of research infrastructure services.
RACHAEL KOTARSKI: That covers services we are building, such as a shared repository service, which I'll talk about in a bit more detail. It also covers work looking at persistent identifiers as key research infrastructure. Again, we'll talk about this identifiers later as well. We lead the UK consortium for DataCites. We were a founding member. And so representing different kinds of research outputs as first-class research outputs has been something that we've been trying to do really back since the early 2000s.
RACHAEL KOTARSKI: We are also an active research organization ourselves. So we have this particular role, independent research organization, or IRO. That means we're eligible for government research funding via UK research and innovation, but we do also undertake projects from charitable foundations. So the image on this slide is a little image from the summary of research that was undertaken at the library between 2018, 2019.
RACHAEL KOTARSKI: The latest research year we have very recently released due to some things that delayed lots of reports for some reason. 2019, '20 has just been published. But, yeah, this kind of shows where we were up to up to 2019. And our role as an independent research organization means we're not actually needing to report things into the REF. We do, though, want to adhere to and do need to still adhere to open scholarship practice and mandates, even though we don't necessarily have that REF impetus there.
RACHAEL KOTARSKI: But research that we undertake and practice research that other heritage organizations undertake actually informs our business as usual activity. And the kinds of outputs that are listed on this slide, those are the items that we're keen to make available, mandates or no mandate. So if we move on to the next slide. Thank you. With our shared research repository, we aim to support galleries, libraries, archives, and museums.
RACHAEL KOTARSKI: That's what the "GLAM" stands for, for those who aren't familiar. And we are working in a shared research repository on a platform called "Hyku," which is itself based on Samvera, so it's an open-source community repository project. And we wanted to create a space for heritage research where we could have independent tenants within a single technical platform and make all of our research available kind of live nationally and internationally recognized brands.
RACHAEL KOTARSKI: Some of the organizations that we work with, we're working with The British Museum and Kew Gardens. They're recognizable brands. We want to be able to have a recognizable place for their research but also give us an opportunity to pull together all of that into one place and have a single search point for all kinds of heritage research. With the work that we've done so far, we do already have some representation of practice space outputs, specifically around exhibitions and actually the content related to exhibitions.
RACHAEL KOTARSKI: So events that we might hold, exhibition catalogs, it really is a kind of a type of portfolio activity with lots of digital and analog, physical items and outputs as well. So if we move on to the next slide, I mentioned that it's quite important for us to have a bidirectional link between practice-based research and actual practice itself. So the research actually informs how we might conserve our collections, as demonstrated in these images.
RACHAEL KOTARSKI: And it is, therefore, important that we are able to replicate and closely reproduce the practice-based research outcomes that we're seeing out there from the academics. But at the same time, our practice professionals, if you like, are in their day-to-day activity producing some outputs, technical manuals, other guidelines that actually would inform practice-based research.
RACHAEL KOTARSKI: So we want to have that virtuous circle of practice, research, and academics feeding into professional practice and background again. And we also want to empower our colleagues who are undertaking practice on a daily basis to think about how they can support their research colleagues, if you like. So if we move on to the next slide. Some of the limitations we found in developing our repository platform as it stands at the moment I think is more borne out of the fact that we've tried to follow existing work in the repository sector, make decisions because they're familiar to users of repository platforms, familiar to the sector.
RACHAEL KOTARSKI: But we do actually also recognize the need for new approaches and especially new standards. Again, I think the portfolio-style approach, having one record that needs to cover and exemplify a range of outputs and practice. So the example I've got here is object labels, exhibition text, exhibition catalogs, how we did the conservation of those items to get them into a displayable state, podcasts, events, artist-in-residence programs, bringing all these together in ways that enhance discoverability, enhance the understanding of what we do as organizations, and again make things reproducible and replicable are important to us.
RACHAEL KOTARSKI: So that's just a fly-through of the concerns we have at The British Library as a kind of heritage organization feeding into this. And I believe I'm now handing over to Adam.
ADAM VIALS MOORE: Hello indeed, yes. So my name's Adam Vials Moore. I'm the product specialist for persistent identifiers at Jisc, which is a UK organization that supports further and higher education in the UK. So it's UK for UK. I'm going to talk a little bit about the underlying work that Jisc does in this area. And then I want to talk about the metadata persistent identifier standards and where are we currently are with regards to practice-based work and where we can address some of the issues that Jenny and Rachael have talked about.
ADAM VIALS MOORE: So again, I've been working on practice-based research for a couple of years. But with my background in kind of technical arts and so technical ethnography, which basically means looking at my own practice in using technology, I've been interested for quite some time in this as well now. That's a lovely picture to start off the talk.
ADAM VIALS MOORE: And it's kind of capturing what we've been looking at in just under the auspices of the five key persistent identifiers that we have been supporting the development of, those kind of key within the underpinning of the whole scholarly infrastructure for the UK, looking at the personal identifier for ORCID, the work done on ROR for identifying organizations, the work on the Crossref grant identifier, working on DOIs for identifying works themselves, and RAiD, which I'll come and talk on a bit more later.
ADAM VIALS MOORE: But kind of RAiD as the idea of identifying a project, of grouping things together in a basket for other identifiers is really important for the work we're talking about here. Just there on the right, it's a link to the note of record for the cost-benefit analysis, which we produced which shows that supporting these persistent identifiers by encouraging their use and embedding them across the infrastructure can save research significant time and cost.
ADAM VIALS MOORE: So go to the next slide, please. So given everything that's been said before, what do we want to do to kind of, as Jenny said, change the world and fix all this stuff? So a lot of kind of the origins of the metadata and persistent identifier PID landscape is grounded in text, grounded in STEM, and it's kind of evolved from a place.
ADAM VIALS MOORE: And that's kind of where we've come from. OK. So what the next phase of this is to kind of get some constructive ideas together, think about what's currently working, what's kind of working in our favor right now, what's kind of in progress, and where we've got a call to action, something that we can say let's do this and work together.
ADAM VIALS MOORE: Where can we expand? Where can we address needs to bring practice research, non-textual outputs into our space? Let's not build something else, have yet more standards, and yet more change to like integrate stuff into infrastructure itself but build out and create inclusion instead. So next slide.
ADAM VIALS MOORE: So what I'm going to do is go through a number of different kind of PID and metadata things and talk about them individually. So I'm going to start with ORCID. I was, for a couple of years, part of the team supporting the ORCID consortium in the UK. So what works at the moment? Well, there's a great process for looking at the work types in ORCID and discussing where and how there should be new work types to identify need and add them in.
ADAM VIALS MOORE: And there is also an open and willing community process for that. So in 2020-- I was going to say last year. Two years ago now, we held an event as part of our consortium community. And as part of that, we identified the non-text outputs that was in need of not just being other and that it needed to be expanded to be a more fine-grained listing.
ADAM VIALS MOORE: So we've moved other out of like a space. It says "other" at the bottom. We're working with ORCID itself to kind of ensure that that's embedded more fully in the work types. And what we need now is to ensure that we've got use cases and user stories to ensure that those categories and new resource types are embedded within the ORCID taxonomy. Next one, please.
ADAM VIALS MOORE: Now, so as Rachael mentioned-- I shouldn't really be talking about this. Rachael should. But the latest version of the DataCite resource types has really worked hard to reflect what's going on in kind of the scholarly outputs landscape. And the Metadata Working Group has actually been looking at kind of the things that are there, and we've got resource types that reflect the range of outputs that are in practice research.
ADAM VIALS MOORE: So we've got AV collections events, interactive resources. You can see that list. But again, what we need is to bring together the community to make sure these use cases and user stories are there to feed into the requirements process. You'll see a couple of times the mention of the word "bringing together a community." I think Jenny mentioned that we have recently been funded for an HRC project.
ADAM VIALS MOORE: I think you may hear mention of that again. OK. Next slide. So the Research Activity Identifier, or RAiD, is a project identifier. So it has an actual identifier and then the metadata envelope. Now, RAiD is incredibly important to this space, because what it allows you to do is describe the kind of overarching handle to a narrative.
ADAM VIALS MOORE: So you can have kind of like a washing line on which you hang everything on. So you can say here is my project, my piece of practice. Here are the people who are involved. Here are the institutions that are involved. So here are the ORCID ID and RORs, if you like. And then here are some outputs. Here are their DOIs or whatever references you want to use. Here is the other bits and pieces you can go down to, particular institutional IDs if you need to use them.
ADAM VIALS MOORE: And what it gives you is a set of reusable open identifiers related to a single identifier, which says here is the actual narrative itself. We will be looking at using RAiD in the pilot alongside our project. And we will be working with the RAiD community as a part of that steering group to ensure that it actually works with our kind of use case.
ADAM VIALS MOORE: And again, community use of cases, user stories, it's important to feed into these things. Next, please. So Crossref is, of course, global and huge and 99.999% of content metadata, something like that. I think it's about 97, actually. So they've just recently, well, six eight months-- it's pandemic time, it's not real time.
ADAM VIALS MOORE: They talked about the nexus, and that's been a really useful example of like linking all these different kinds of information and content types together in a really open manner. It's been a really useful way to showcase how, with this huge amount of content, everything can be linked together that you can refer to. And for us, it's really encouraging because Crossref is one of our project partners.
ADAM VIALS MOORE: And again, Crossref are really interested in ensuring that all of their content is available in an open way. That's part of their main mission statement. So we're hoping that, as part of a content advisory group for practice and other kind of non-text outputs, that will inform the kind of shape of their content and their kind of vocabulary and taxonomy. Next, please.
ADAM VIALS MOORE: So to me personally, as a long time postdoc, credit's very important. It encapsulates this idea as the role as an important part of the scholarly record, where your actual contribution is something. Currently, it's a consultation. It's happening from its kind of version one transfer to NISO from its very, very STEM beginnings in that it originated out of medical schools to broaden out of these like kind of conceptualization investigations onto more kind of wider role descriptors.
ADAM VIALS MOORE: Again, there are other rule taxonomies that are much broader and recognize a much wider range of rules. So we very much hope that credit working together with those other taxonomies and communities again will evolve with the correct input of those communities and use of stories. Could probably just record that bit and do it again. Next one, please.
ADAM VIALS MOORE: So metadata-wise, I think this is both incredibly important and quite frustrating. So COAR, CO-AR-- there's about four different COARs. Aren't there? So COAR does include some non-text resource types. But it's got that other thing in again, which you'll see from some of the other work that we've put out.
ADAM VIALS MOORE: I'm not fan of. And it's part of this evolving, I guess, project landscape. But the thing about it is is that-- we'll come and talk about discoverability in a bit. It, again, needs more granular resource types. OK. Next slide, please. Now, rioxx has evolved as a really great direct embodiment of the content of repositories.
ADAM VIALS MOORE: And version two got many repositories through REF submissions in version three of the taxonomy. After quite a long hiatus is now like out for consultation. But again, it's an embodiment of repositories as they have been. And one of the things that we are kind of addressing in the project that we're talking about is that repositories have struggled to reflect practice research.
ADAM VIALS MOORE: So what we really need to do is work closely with rioxx to ensure that that vocabulary is broadened to kind of anticipate the work that will reflect the ability to capture that content so that, again, the non-textual stuff is there and available. So that kind of, as the repository evolves, rioxx will actually be there to support it so that those two things can hopefully at best would occur contemporaneously, which is a very long word for this time of night when I'm recording this.
ADAM VIALS MOORE: Next slide, please. So again, just having a think about these implications for discoverability. So I mentioned this whenever I talked about CO-AR, COAR. CORE harvests those PDFs only. So for the metadata, it's looking at them. It mostly uses rioxx, because a lot of the OpenAIRE things don't really give you the quality you want.
ADAM VIALS MOORE: And again, it only will label the things using the tags that are there. So again, that metadata needs to be there in order to enhance discoverability. CORE can build a custom search that could look at some of these things. But again, then they need to be in the repositories and they need to be available and they need to be a PDF, which, again, not really any of those things for quite a lot of the actual deposits that we're talking about.
ADAM VIALS MOORE: And Google Scholar, the ongoing Google alpha project-- I don't know if any of the rest of you watched that recent webinar with interest-- is still an alpha. Still could go away at any time. Indexes text when they're less than 5MG with one file. So really, again, this is a lot of the thing that people are kind of relying on for kind of the great literature of the work that's outside of the official indices.
ADAM VIALS MOORE: But again, it is itself incredibly unreliable. And it just has this piece where you're kind of worrying about whether or not it's going to be there tomorrow and whether or not it's actually finding in the first place the things that you're going without you kind of again directly kind of depositing, pointing to these things, these kind of ideas of things being able to be discovered are quite difficult.
ADAM VIALS MOORE: I think one of the other things, just briefly on like this whole kind of thing, again, from all the things we done, I don't think what we've identified at any point is a need for a new standard for any of those things. So what I'd really appreciate having listened to this, if you could think about the adjustments that need to be made here, the adjustments to taxonomy, vocabulary to usage age and integration.
ADAM VIALS MOORE: And again, I'm sure Rachael and Jenny will speak if I in any way kind of misrepresent it. But what we want is to include to build things that bring in rather than build another standard, which has to be added, which has to be adapted and adopted and verified.
ADAM VIALS MOORE: And I think all of the things that we've discussed, the metadata, the persistent identifier structure, the basic underlying fabric, there are places for inclusion and addition rather than the need for a new thing to be added, created to address any of these issues. Next slide, please. I think this is where I hand over to my colleague, Rachael, to discuss about the actual project.
RACHAEL KOTARSKI: Yes. And much like Jenny describing how this work has been going on pretty much for three years now and I feel like I'm just swooping in at the end when there's a chance to take some of the glory, I feel like I'm doing that with these slides slightly as well. But I think that we've shown you how we want to move beyond the other of practice research. And with the specific project that we're just embarking on now, Practice Research Voices, we want to be able to make practice research outcomes first-class research outputs.
RACHAEL KOTARSKI: The project is funded by the Arts and Humanities Research Council to produce further recommendations so that we can make concrete changes to the tools we use to communicate research. And when we talk about those tools, we mean repositories, yes. But we also mean standards, ways of exchanging, and linking these output and the data that they contain. So Jenny is the principal investigator on this project.
RACHAEL KOTARSKI: Her colleague, Neil from Westminster, is a co-investigator as is Adam and myself. And we also have another co-investigator, Professor Helen Bailey, who is our kind of friendly practice research-based academic. There are technical partners to help us, Westminster specifically, with developments towards improving repository support. And Adam's already mentioned Crossref being a partner on the project.
RACHAEL KOTARSKI: We also have the Victoria and Albert Museum, who have some great projects that will help us to really understand requirements and test some of the approaches as well. So there are three strands to this project, the first of which is repository. So as I mentioned with technical partner to actually, once we understand requirements and needs for practice-based outputs, actually being able to iterate to repository platforms and technologies in response to those requirements, test some of the recommendations, et cetera.
RACHAEL KOTARSKI: We'll be doing some of that as well within The British Library's repository and within Jisc's repository, trying to get us towards those fair principles of practice research. Strand two is looking in more detail at the work Adam's just presented around the metadata and the persistent identifiers landscape. We want to work with these organizations and, more importantly, the communities.
RACHAEL KOTARSKI: So as Adam showed us, there are lots of these persistent identifier metadata standards, vocabularies are working with community groups already. And actually, we want to feed into that ongoing process so that we can move the conversation in the direction of practice-based research and outputs beyond text as well. We are planning a metadata workshop, because that's a key part of the work. And we will announce that on all the platforms where you can reach us for the project.
RACHAEL KOTARSKI: So as soon as we've confirmed a date with that, please do join us. And then strand three. All of those existing kind of community discussions with metadata standards, persistent identifiers, et cetera, will take and willingly listen to and respond to communities when they say they have a need. And I think what we want to do is to create a practice-based research community of practice so that we can kind of speak with one stronger voice about what the needs of the community are to help make those changes.
RACHAEL KOTARSKI: If we're trying to speak to various infrastructure providers and it's one person over here saying one thing and then someone slightly to the side, kind of has the same requirement but they don't articulate it in the same way, we're not going to make as much progress as if we can actually speak with one kind of coherent voice. And that's not to say we'll all want the same thing, because I'm sure we won't. But actually, if we can work together as a community to demonstrate needs and communicate them to whoever we need to communicate them to, that will make the work much stronger.
RACHAEL KOTARSKI: So we definitely want people to come and join us and, yes, join in our chorus, as it's put here. And that's it from us. Thank you. [MUSIC PLAYING]