Play the webinar
Play the webinar
Register for the webinar
January 27, 2023
This webinar describes Figshare’s open features and also covered future aspects of Figshare that are planned as open source. Topics included community driven development, planned open source features, and free accounts for researchers around the world to further collaboration.
Please note that the transcript was generated with software and may not be entirely correct.
0:03 Hi, everyone, and welcome to the Figshare webinar today. I'm here with Andrew McKenna Foster, who is Product Specialist at .... I'm just gonna give it a few more minutes forever. Few more seconds for people to get online. And if you can't hear me or see me or if you can't see Andrew size right now, please just flag and the child, the Q&A box and we'll try and get any technical difficulties and out before we stopped.
0:33No complaints so far, looks like all is well.
0:40 The numbers are quite a few online, so I'm gonna start with the housekeeping bits, and then I'll pass over to Andrea for today's presentation. So, as I'm sure you can probably tell, you all in listen only mode. But if you do need to communicate with me, you'd like to ask a question, or to some clarification. You can use either the chat or the Q&A function in your control panel on goto Webinar, and I'm going to monitor both throughout. We will have time for Q&A at the end. But if there's something I can address over the chat, then I'll do that throughout.
1:15This session is being recorded, so if you have to drop off at any point, or if your colleague wasn't able to make it, we're going to share that recording probably Monday or Tuesday next week, so you can catch up at your leisure.
1:27And I think that's about everything for me.
1:30So I will pass over to you and check, thank you.
1:36Great, thank you, Laura. Hopefully my sound is OK.
1:40I'm actually going to drop off video as well to start the, to go through the slides just from that, um, you don't like a little video distracting.
1:53So yes, thank you again Laura, and thank you all for being here.
1:58We organized this webinar because we wanted to give some insight on the role that Figshare plays within the greater repository ecosystem.
2:08For those of you who use FIG share, hopefully this will give you some insight in how Figshare operates and for those of you who are new to FIG share, I think this will be a great introduction.
2:22So today, I'm going to talk about two components that we think partly define an open research repository.
2:30And the first one is that the repository platform operates openly.
2:36And the second one is that the platform enables open research for everyone. So Figshare is an open research repository platform. And I will talk about how it achieves both these components over the next 30 minutes or so.
2:51Picture is a mission driven software as a service repository blackcurrant.
2:56So what does mean basically is we are confident that the value we put in is greater than the value that we take out.
3:02So our goal is to help institutions and researchers share the research outlet's persistently and responsibly.
3:10So, the first half of the webinar, I'll talk about how to Figshare your operates openly and address some of the questions that we get around this.
3:19So I want to start with product development, Big Share has an expert driven product development model that incorporates user feedback.
3:28The repository landscape is changing rapidly.
3:31There, new technical needs, there are new standards that need to be considered so that our team works on behalf of our users, partners and our clients to build a cohesive and really realistic platform and product roadmap.
3:45As you can imagine, the team must balance and prioritize both the technical needs, but also all the community needs and requests.
3:56So, there's this help page which describes how this works, how we do this, how we collect information, and how we prioritize information, and I've listed the, what our product director calls the pillars that they use to prior prioritize the various requests and needs.
4:15Of course, security, policy and legal, things are all at the top, but the list also includes things like quality of life improvements, value to clients, innovation, and sustainability.
4:26So this QR code will take you to that help page, or you can just search the Figshare help site and you'll find it.
4:35So, importantly, Weller developers are driving the ship.
4:41Big share, the Figshare community really plays an integral role in guiding the future functionality of the platform so the product team gathers information and feedback through a variety of means and you can actually see them listed. here, This is another screenshot of that same help page.
4:58Um, but these things include, ..., in person, or virtual, excuse me, working groups, one-on-one meetings. There's a community Slack channel, which you can see here on the screen.
5:11We have a feature request form, which is feature requests, not just from institutions using picture, but also just are just global users using the platform, as well.
5:22So, we also have live documents for comment.
5:26So this QR code will take you to the future of metadata document, and read about what metadata might look like in the future and picture, and you can leave comments, Leave your opinion there, as well.
5:39So the gentlemen tickets, as you can imagine, huge amounts of information, huge amounts of feedback, and requests from all of these means.
5:47And our Project director, I think, does a really heroic job of maintaining this public roadmap, which is at this QR code. So you can visit if you haven't been there already.
6:00Um, each little card on this map provides information about that feature, or an enhancement.
6:09Sometimes, I'll have a longer description, and if it's linked to a feature request, we'll actually give you the link, so you can go and actually see the feature requests, which is really nice.
6:20Now, of course, things do change on this map.
6:22On this roadmap, as, you know, needs evolve.
6:26Some features take a long time to develop. They might be technically complex. They might have a dependency. That has to come first.
6:34But other things can move really quickly.
6:37And I have an example of that.
6:40So over the last few years, picture is starting to be used, a lot more as a full institutional repositories. So not just for data but papers, theses everything. And batch management of metadata, and files, within the interface was something that we saw a lot of requests for it.
6:59And so, in the winter of 2021, a product director sign, an opening in dev time.
7:04You know, there's a short window where there's some dev resources available, was able to swipe this in there.
7:12And so in the, in around December of 2021, a document went up or administrators, you know, institutions using ... to provide comments and ideas around what this, what an admin patch management tool should look like and how it should work.
7:29And then basically within, within six months, we had a nice new tool available for use and this was able to move quickly because it had few dependencies. And then as I mentioned, there was this, there are some dev resources available.
7:45Now, I know, I think this is really exciting. We actually already had a, an institution use this tool to migrate into FIG share. So they actually just launched this week. That will vary college. They use this batch management tool to do their migration.
8:00Just really nice to see.
8:02And by the way, we have a webinar coming up in early February with like tips and tricks on how to use this tool. There's also a whole page with little videos.
8:12So there's lots of help information out there, But the webinar, we'll have, just, you know, help me help you walk through some of the things that people may not know about this tool.
8:24So another way that FIG share operates, openly is through the openly documented two-way API.
8:31An API is an application programming interface that allows you to access information in a way that bypasses the, the point and click User interface, it's great for automation, reporting, building tools, and I think it's pretty impressive that this has been part of the picture platform. Basically since the beginning for all the 11 years that Figshare has been around. It's been part of this platform to provide as much access to the metadata files as possible.
9:00So, they're endpoints that enable programmatic upload management and download, Um, and repository admins can actually do some, perform some management tasks through the API, as well.
9:13There are things that you can do in the API now, that will eventually be in the interface. But, it's just easier to have them in the API for now, and make it available.
9:25So, an example of that is being able to upload an existing DOI to a record can do that through the API. Eventually. that'll be in the interface.
9:37Any user can use the API. You can just create a token through your, through your account.
9:42And one reason this is really useful is that for an institution, there's no lock in of data, So institutions can download all of their metadata, all of their files at anytime, without Figshare yourself, although we will help you if if you want that.
9:59So those were a few of the ways Figshare operates openly, but I also wanted to take a few minutes and address a question that we get a lot around open, which is, why isn't fixed share's code open source?
10:17There are multiple reasons for this, I'm going to talk about 3. 1 is that there are benefits to one master code base.
10:26It allows us to produce consistently, high functioning, policy compliant infrastructure.
10:32So, if we were open, there would be lots of versions of the platform out there that weren't necessarily ticking.
10:38All the boxes for compliance and functionality, and the out of date, or unsupported versions really would not be delivering open data in a consistent way that the current picture platform does.
10:51Another reason is that open sourcing the codebase would take at least six months, and it would take the entire team basically to do that.
10:59And instead want to spend that time.
11:02Building new functionality, focusing on keeping the platform running perfectly, and offering better services to users and clients.
11:12Ultimately, though, one of the main reasons is sustainability, Figshare, Founder and CEO, Mark Hahnel chose not to pursue the open source route with sustainability in mind, and this is not to say that open source isn't always sustainable, but Mark said, this is a good way to make sure that FIG share is around for the long haul.
11:35So being able to license the software helps ensure long term financial stability and sustainability.
11:42Make sure devotes resources to ensuring security available availability and stability of the platform.
11:49The developers, as I kind of just mentioned, are constantly developing enhancements and features.
11:54And our support team is answering hundreds of tickets every month, from no basic questions to configuration requests or questions.
12:03So, this is a big investment every year.
12:07Big shares here for the long term.
12:09So, knowing that the cost of development, maintenance and infrastructure are covered is really essential.
12:17I'm going to keep going on this line for just a moment.
12:20Another perspective on why sustainability is really important is that picture is more than a tool.
12:26It's digital research infrastructure, at a global scale.
12:30There are hundreds of thousands of users around the globe.
12:34And the platform is research critical outlets, things that are cited.
12:39There, datasets that people need to access.
12:42So we want everyone to be using same up to date version of the platform, so that everything functions properly, all the time.
12:49If something doesn't work, potentially affects thousands of people, and it could be a barrier to the research process, which we don't want. We want people to be able to re-use data and datasets. You know, we want to be this hand supporting the tree here. We're going to serve the community as a foundation of the digital research infrastructure.
13:08So this means providing, it's absolutely essential that we provide the reliability, stability, and availability of the platform.
13:17We can do that really well through financial stability and maintaining one code base.
13:23Having said all of that, there are some open source features coming, so this is really exciting.
13:30Uh, this is through the Generalist Repository Ecosystem Initiative, which is a big project funded by the NIH.
13:41It's a collaboration of seven generalist repository platforms, including Picture.
13:46A major goal here is to increase metadata interoperability.
13:50And so FIG share is contributing multiple features. And, you know, this, this list here is not, doesn't you scratch the surface? It's definitely not all of them.
13:59But things like full text search, being able to put a context on the reference links, adding Research organization, Registry IDs for author records, maintaining folder structure within a record. All these are coming, and they're going to be open source.
14:14So, that's really exciting, exciting.
14:18So, while we're on this topic, then, I, then, I'm gonna move into the second component.
14:25I did want to wade into the territory of costs around operating these platforms.
14:33So there's always been this question of, are open source systems cheaper, and it's extremely difficult to answer.
14:41Here are four, uh, resources that I know about, that kind of dig into this, and try to answer this question.
14:51That, uh, resource on the left is a survey.
14:56It's the Eclipse they surveyed a bunch of folks who run repositories trying to find out what their costs are. The middle left resource is a book chapter that does literature review, and then has some case studies.
15:08The royal society link lifted repositories at different sizes in different areas.
15:14And then the the AOI site kind of digs into like how they're approaching this. This issue, this, this question.
15:25The takeaway, though, is that it's really difficult to gather comparable cost data, for example, an inexpensive platform, whether that's an inexpensive license fee or uh, there are many resources devoted to running it, yeah, it's generally going to lack some of the functionality that you could have.
15:41Um, then, there are other things, too, like, how do you value flexibility? How do you value your own internal resources?
15:49How do you value your overall values around software?
15:53So, but when it comes down to it, based on some of these resources, the annual cost of repository could be 100 few hundreds of dollars per year, to hundreds of thousands of dollars per year. So, that's, that's what folks are spending on running various repositories.
16:08But in general, I think many of us know this, proprietary systems have an upfront license fee, but usually lower staff and infrastructure costs for the institution.
16:18So the true cost of those things, part of the license fee bundled in, they're kind of hidden by it.
16:24And then these systems usually have higher expectations around availability and functionality. Then an open-source option, the software is free. So the upfront cost may be lower, may appear lower, whether you're paying a third party to run the software or doing it yourself in house.
16:41But the staff and infrastructure costs can be higher, or you're paying a third party to install the functionality that you want.
16:48So, there's the potential for it to get really, really expensive.
16:54So, of course, it's really important that some institutions and organizations can devote the resources to open source development to benefit others using that, that platform.
17:05But it's also really important that there are others who can't devote those resources. Maybe they want to, they need to devote the resources to another important area in the research ecosystem.
17:15And on the Figshare side, we aim to keep costs as low as possible while providing the best possible platform and services. You know, we want to be an option, We want to be a responsible partner here.
17:28And actually, along these lines, you know, we exist with open source options. That's part of being an open repository platform.
17:36I think, know, we want to play well with others, Wouldn't be a core part of this repository platform landscape. I mentioned the gray Project, General Suppositories Ecosystem Initiative, That's a great example of this. So, we're not here to create a silo, want to break down silos.
17:54We want to help data sharing and Open Science across the board.
17:58So, you know, for those who can afford develop resources, or require little configuration, open source repository systems might work.
18:05Those who want functionality off the shelf, want to devote developer resources elsewhere or can't afford the human capital to develop those systems. Picture makes sense.
18:15We have a lot of folks who've done this around the world. Over 100 research institutions thunders and agencies using Figshare.
18:22I do want to say that for those who do use picture or considering using feature, there is sometimes the question of what this picture do with my data.
18:32So thought we'd answer that in this webinar as well.
18:35Your information is not for sale or Figshare
18:38So our business model is, it's not about repurposing your data and and selling it.
18:45We are solely a platform to help you make your research outputs discoverable and suitable.
18:51So I have one more slide for this, this first part.
18:56And just to cover another question that we often get, which is what does the license fee cover?
19:02As you might expect, it covers all the ongoing development and maintenance there, you know, between 8 to 16, um, feature releases or maintenance releases every year.
19:15There's no downtime, unlimited support, and the license fee also covers infrastructure costs, and storage, and cloud compute costs.
19:26If you're using picture storage, so, you know, every time a file is downloaded, there's a cost associated with that. So, that all gets bundled into the fee. So, these are costs that any platform pieces, whether you're paying for a license fee fee, paying for it, paying a third party to do this. Or you're devoting internal resources.
19:50OK, so, I'm gonna move on to the second component here and I just laid out how to Figshare your operates openly.
20:00I want to talk about how feature enables open research for everyone, and this builds on everything I just talked about, because the sustainability and operation of the platform is vital to Figshare your role in facilitating open data and open science at a global scale.
20:18What do I mean by this? Like, what does this look like? An open research repository platform should allow and it should help anyone to make the research outputs discoverable, suitable, re-usable and it should also provide options for integrations and workflows that can streamline the research output sharing process.
20:40Make sure it's always had free accounts. That's how it started as a service to individual researchers.
20:48This is about global quality and access. All that you need is a last name and an e-mail and of course you need Internet access.
20:55Um, but if you have those three things, you can create a free account and start sharing your outputs.
21:01Then FIG share commits to making these records publicly available for the long term.
21:06And we want to do that in a responsible way.
21:12So no files are stored in three locations using AWS S three.
21:18There's a preservation system setup for these free accounts For institutions using Figshare.
21:25We, uh, the API basically allows them to use their preferred preservation system.
21:31So the result is a global collection of discoverable research outputs. It's not just outputs from institutions that can board repository infrastructure.
21:44By the way, I put the Earth images, south side up just because, you know, our usual view of Earth is arbitrary.
21:51I was inspired by seeing a lot of astronomy podcasts recently.
21:56So because we have these individual accounts and these institutional accounts, and they're all basically linked pictures, this vast Global network research outputs, when you search FIG, share through the federated search, you have access to research from around the globe North and South.
22:11At the same time, if you use picture as an institutional or data repository, your records are accessed by the world through this same search interface.
22:24So, this is a these are images of a few of our institutions around the world, using picture, as well as the public profile images from various folks with free accounts on picture dot com.
22:35So, again, huge diversity of research, all available in a discoverable way.
22:39And actually, a little later, in this webinar, I'm gonna write an example of how this kind of a network can help with re-use.
22:49So this is discoverability within the fake share federated search.
22:53But for open research, that's not enough.
22:57Um, discoverability across the Internet across the digital universe is really important.
23:05So, a repository is not just a place to store records. It should be making them discoverable everywhere. If you do, you do open research, if it's not findable, you're not gonna see re-use.
23:14So records and Figshare are highly discoverable outside of the fixture platform that your pages are marked up to be discoverable in major search engines in a variety of indexes. And the development team works really hard to make sure these pages are up to date with the current needs of those search engines and indexes.
23:37Another aspect of making sure we're helping folks with open, open data and open research, is creating fehr records, so findable, accessible, interoperable, and re-usable.
23:51And Figshare helps create fair records in multiple ways.
23:56We have a standard standard metadata fields that can be mapped to other metadata.
24:03I think this one's really important. The metadata schema that's used in Figshare is simple but also descriptive. And this is actually why I first use FIG share when I was in Library school.
24:15You don't need a PHD in library sciences to fill out the metadata while also properly describing your files or resources. So this is accessible to the average researcher. It helps everyone create fair records.
24:30Additionally, every record has a DUI or handle, it has a persistent identifier. Every record has a license both. These are both really important components of fair records.
24:41Then, the records can be linked to a variety of other persistent identifier services, and there's grant linking, and there are metrics and metrics for the reporting on the rates.
24:56I mentioned this a little bit earlier, But, uh, another aspect of being an open repository platform, is that the metadata in files can be accessed in multiple ways.
25:06So a user or a human can access them through the, the point and click your user interface, and a machine. Or software can access them through the API.
25:21Um, so, and all this can be accessed as appropriate. So even, you know, a user can actually access their private files through the API with a token. They can log into their accounts, et cetera.
25:35And the API enables integration with workflows and researcher tools to try to, you know, make this whole process easier, and and smoother and more efficient for everyone.
25:51So, I'm actually going to, and by talking about some examples of how this has been done.
25:58So, you know, I think that some, some might look to, for an example, on open source option, because they want to build on it, they want to customize it. They want to make it their own.
26:10Um, this option is available with Figshare through the API.
26:13You can build the tools, the innovative tools, the efficient workflows on top of the repository because we have this open, open the document at API.
26:24So I'm gonna share some examples of that.
26:27Um, and then, and then I'm sure there's going to be plenty of time for questions.
26:32So the first example is, this tool.
26:37It's actually a custom kind of submission workflow developed by the University of Arizona, on GitHub's QR code will take you there.
26:47It's really nice. It works with the ...
26:49form, gathers information, and creates a readme file, as the researcher is getting ready to submit records into the repository. So a nice way to help the curation team.
26:59Um, create the types of records that they want in their repository.
27:07Uh, the University of Sheffield has created a fully custom interface, search interface, as well as some reporting, so for, for researcher, metrics, using API to, to fill in, and put content into their own custom web pages. So it's really nice. I love kind of scrolling through and checking out how, you know, all the facets of added and various other things.
27:35So, this is a nice example of if you take it no, to some of the highest levels in terms of customizing how people are interacting with your repository.
27:47Macquarie University created a tool also in GitHub to harvest records, harvest their institutional records and Dryad inquiry catalog records in their Figshare powered institutional repository.
28:01And so here are some QR codes for these various links here.
28:05This is really nice. So it gathers the metadata, leaves the files.
28:09With the original record of course, it creates catalog record in the repository that points to that original record. You can see in the rate screenshot, it, it puts the link on the DOI link in kind of the main preview area, and then provides all the metadata down below.
28:29And then a final example is a really recent example.
28:33This set of researchers use the Figshare API to automate the searching coalition of these geochemical datasets and they were primarily gathering this information from journal sucks supplements.
28:48So from various journals that use picture or offer a Figshare repository for authors submitting manuscripts who need a place for their datasets.
28:58So this group was able to gather all these datasets and create one compiled dataset.
29:05And then they use that to offer some advice on how, you know, how to name the variables in a more consistent way to make re-use better.
29:13And this was possible because the API provided search access across all of these different repositories.
29:20Now, there's also, I wanted to do a little side note on this, too, because I found this very interesting in terms of re-use, that the, of the 500 plus datasets they gathered, three licenses were represented.
29:33There, all Creative Commons, Creative Commons attribution licenses, maybe one was not an attribution. And then a third one was non commercial.
29:43And, because, you know, because they have these different license options.
29:46Their final compiled dataset a, they had to put the most restrictive license on it, which was the attribution non commercial.
29:54And so, it's a, and they mentioned this in the Paper.
29:57So, it's a nice, kind of clean example of how licensing an individual dataset can have ramifications down the line for those aggregating datasets and trying to re-use them altogether.
30:12So, finally, you know, I've mentioned the API quite a bit in this webinar, and I think it's a great way to build on the picture platform.
30:19And, and it really makes it your own, we do have a help page for those who maybe are new to APIs that can get you started on this, So this QR code will take you there.
30:31There are actually some example scripts and other advice and tips there, if you think this could be useful, I want to try this out in your own repository or with your own pre Figshare account.
30:44And, with that, I think, maybe, like, even just a little bit earlier than 30 minutes, so, I'm going to end there.
30:51Thank you, again, everyone, for attending the webinar, or watching the recording, and if there are questions, or I'll, I will, attempt to answer some questions.
31:04Hi, Andrew. Thanks for that. We haven't got any questions in the chat, as of yet, and we'll just give it a couple of minutes for any come through. And I'll just check both boxes, as well. And, of course, Andrew's details of the results if you think of any afterwards. Oh, oh. I have one. How can we go about signing up for the Slack, Which I can help that, Actually, Angie and there was a follow up with you and send you an invitation to the community sack afterwards.
31:35And we have another one. And is it possible to get citations for the cost of open source systems?
31:45Oh, yeah, I was like, debating, it was like, should I put QR codes in here? Should I, not? Yes. Or maybe I can.
31:51Well, maybe we might be able to share the slides, too, in our team picture may be, which all those are there.
31:59But, yes, we can definitely follow up with those. Yeah, I'm sorry about that.
32:06And in the recording, those are, I think they're pretty highway access sites.
32:10So if you just search the title, I tried to put in as much information to be able to watch the recording, it, the information from that slide, quickly find those resources.
32:24Thanks, Andrew. And another one hair and simplified metadata. I missed if it was based on an existing or structured schema.
32:35Great question. Yeah.
32:36Our fields are based on the data site, metadata schema, um, and they're all standard fields.
32:42So they can be mapped two other schemas.
32:45And then from the record pages, you can download the metadata in different formats like W or are National Library of Medicine and entered the API, the OEI PM, each. There other formats available through there.
33:00And the API provides everything as JSON.
33:04Thanks, Andrew, and another question. Hey, Jim, not sure I know the structure. If you already have another digital science to IE dimensions, do the accounts carry over to Figshare, or are they set for I believe that completely set or Andrew is that right?
33:21Yeah, the, the one where this does matter is if you're using ...
33:25elements, the current research information system, that's where the accounts will align for the best optimal use for both products, but with dimensions, yet, since that's just an information service, those accounts don't align.
33:44Thank you. Next question, Institutional repositories often have to be interoperable with national research exercise submission systems. For example, the REF and the UK. Does Figshare have that functionality and are just jumping on to do a shameless plug for our webinar that we heard yesterday, which was fixed in relation to the ref, so I can follow up with the recording to that one, straight after this, but Andrew, I don't know if you have any additional answers.
34:13Yeah, and I actually, I'm, I'm based in the US, is probably everybody, easily figure out, so, and I don't know as much about the ref, um, but I think the webinar's probably going to be the best, the best resource for that.
34:29Kean, next question: Is it possible to pull technical metadata out, as well as descriptive?
34:40Ah, yeah, good question. So, there is some technical metadata available through the API.
34:45Things like, um, dates, like some of the dates that you can't modify, like a modified date, when the record was modified, and some of the other, kind of, like, underlying information. Or the descriptive information.
34:59So, like, the category IDs from that taxonomy and things like that.
35:07Um, other technical information is available through support requests.
35:13So we can, no, we can help discuss how, how you can get that information in terms of like a custom report, and that kind of stuff.
35:24I will say, I think for like integrations, with preservation systems, sometimes that requires, uh, being able to, pull in different types of, like technical, data, technical metadata.
35:40Thanks, Andrew, and next question, can you give a high level overview for how an institution gets started with the implementation?
35:49Oh, yeah, good question.
35:51So if you were, to use Figshare, decided to go to Figshare, to power your repository.
35:59And I think I'm going to answer this in a way that you'd like the answer to be, but the implementation really depends, you know, every repository different, and so it really depends on your needs, and, sorry, implementation manager and implementation engineer.
36:15Work with you to understand your structure that you need from the repository, and then how that can be set up with the Figshare platform.
36:26So we use groups to organize things and the different ways to assign users to different groups and different permissions and roles and all that stuff.
36:33So it's a discussion between the Implementation team and your, your institutional implementation team and then we use Basecamp as a project, project tool, management tools, so that everybody knows what tasks are due and deadlines, and there's information in there for folks too to work on asynchronously but also create kind of like a cow a record of communications.
37:00Um, and then there's a Sandbox, staging, environment setup, and can be used for experimentation and testing, and then based on that, start building production version.
37:13Think though, it might hopefully was the answer, but if you wanted, if you're looking for something else, let me know.
37:20Thanks Andrew. Next one more metadata questions does FIG share support, authority, slash controlled vocabularies, link state of functionality, OSC and AF or the IAF identifiers?
37:35OK, I don't know the answer to some of those.
37:38in terms of controlled vocabularies or taxonomies. You.
37:43You can create controlled vocabulary lists and figshare and, uh, Within the last maybe two years, we launched a way to upload really long lists of controlled vocabulary list or a custom metadata field.
37:59And users can select no one option, or they can select multiple options from that list, or that field.
38:05So, yes, you can have, you can include controlled vocabularies in your repository for the category field feature already uses A A taxonomy of fields of research codes.
38:22Um, some of the other examples that were mentioned there, I, I don't actually know what some of those are.
38:31Um, and so I think maybe one answer for that is that custom fields can be used to to provide that information in the metadata record Linking with other services.
38:44I'm not sure.
38:46So if that didn't answer your question satisfactorily, maybe we can follow up with some more information for you?
38:53Yeah, I'll send that one along to Andy.
38:58And I think this is the last one that thank everyone for all of those are great, .... Can you talk a little bit about when what is assigned a handle versus a DOI?
39:08Oh, yeah, great question, So.
39:12So, a DOI, of course, is really, like, there might be some debate about this, but a DOI is really great.
39:20The metadata is stored with the DOI provider, and the provider, then, you can keep that URL at the provider updated, so that it always points to the current location of the record.
39:31And that vita is basically a, you know, let's big organization, it's hopefully going to be around for a really, really long time.
39:38Whereas handles can be kind of a very local setup. So, you can run your own handle server, and assign your own IDs.
39:50But you could easily, like, shut down your server.
39:53And, there might not necessarily be that kind of, like, longer term persistence. Or maybe it's going to Figshare your system, though, every, every record needs a persistent identifier, whether a handle or a DOI.
40:07Handles can be used for open access records that already have a DOI, but you want to give your repository record for that open access publication.
40:17You want to, you don't want to give it a second DUI. Maybe you want to give it a handle. So, that would be one use case.
40:23If you have catalog records, you're harvesting information from other repositories just, and we want to have all the metadata in your repository, that's another time you might want to apply it handles, so that your version of the record as its own persistent identifier, um, then maybe, you know, if something doesn't have a persistent identifier, but you want a, you want a version of it in your repository, and you want to be able to point to that original source, Then you can give your record a handle, especially if you're going to enhance the metadata. In some ways you're increasing the discoverability for that, you know, digital asset out there in the Internet, whatever it is.
41:08So, if, but if it's original research outputs, data, presentation, any type of output that supports research, conclusions, and results, then that really deserves a DOI.
41:23So that's as as re-usable as suitable as possible.
41:32Great. Thank you. A couple more have come in while you were answering that one, Andrew. So this one how long does it take the average institution to get started with Figshare? So from out of the box to first data deposit from a researcher.
41:48Good question, and this totally depends, you know, like, we like to say like setting up a very simple repository is actually pretty quick process. But, as I mentioned earlier, every repository is different. The needs are usually much, much greater than just a quick and easy setup.
42:07So, what we typically say is that, we need at least three months.
42:13two, set up a repository and launch it.
42:17And if you're migrating material in, that's it at least another three months added onto that.
42:22And in that time, what happens is all those discussions and back and forth around, like, how exactly do your workflows work, and how?
42:31how is that going to work with the, the platform?
42:35and setting up the integrations, with things like single sign on. If you have a Chris system that is also a whole nother layer to make sure that that's going to work properly for you and easy.
42:46So, all that happens, that's why the the three month period is there so that, that's generally what we say, you know, migration. You're just setting up a repository around at least three months, you're adding on a migration, that's going to be another three months, about six months.
43:00Um, and, you know, sometimes it goes faster, sometimes it takes a little bit longer, but we really try to to do things as efficiently, quickly, as possible, as, because we have implementations going on all the time.
43:20And this last one do you have any specific examples of new improvements to the Figshare search function, fix your search?
43:31Yeah, yeah, Oh, great. OK, so I mentioned one of the open source features that's coming is full text search. So, that's really exciting.
43:41So, EDS, and I think this is right, PDF will, be, no indexed for search.
43:50That's coming. Another thing that's coming, that's also part of that, The gray projects. So that, I think this will also be open source.
43:57I believe are the two new facets that will kind of be default facets, which are publication, date, and funder, so you'll be able to filter by the funder name or by publication date. So that's exciting, and custom facets are also coming.
44:18Uh, I can think I can say this year, It should be on the, check the Roadmap.
44:24So, that's exciting to so, institutions can have, you know, you have a custom field that you've added somewhere in your repository and you want that to show up as a facet on your repository's Search interface. Then that will be part of that.
44:39So, I'd say those are the, there are probably others, but those are the big ones I think off the top of my head.
44:46Fabulous, Thank you. And I think that is all of them. But I will, after the webinars, I've just because we had a few. I just downloaded more than double check that. We got to. The moon is, not well, and follow up with you via e-mail. And thanks, everyone, very much for joining. And being so engaged with the questions. And, Angie, thanks for your presentation. I think that's it for today.
45:08Thank you so much, everyone. Thanks, Laura.
45:10Thanks. Bye, everyone.