WEBVTT 00:05:05.000 --> 00:05:27.000 Um, and might help me keep the dates a little bit better. But I think the rest of the year looked good. So feel free to use this as a reference. I added the link data discovery SIG to April 10th. If you did not catch that in Slack, they reached out to us about a crossover meeting. They were particularly interested in the link data app and its use of discovery. 00:05:27.000 --> 00:05:36.000 But it might be a good opportunity for us to talk about all the different ways we might envision discovery working with data and folio. 00:05:36.000 --> 00:05:54.000 Otherwise, our calendar is rather open and sort of rolling based on the previous discussion. If there is a topic that you would like to cover, we can set a particular date and time for that, or if there are things people already know they want to discuss in future meetings. 00:05:54.000 --> 00:06:07.000 You can directly edit this or ask me to to drop it in. I'd be happy to do that. 00:06:07.000 --> 00:06:08.000 Yeah. 00:06:08.000 --> 00:06:18.000 I wonder. So we have the column notetaker in the Pc. We we simply we are all kind of, you know. It's rolling to all of us are being the note taker. 00:06:18.000 --> 00:06:30.000 But we fill in our own name, so we then coordinate if there's meetings we are not attending. And so maybe we could you could simply ask us. 00:06:30.000 --> 00:06:31.000 Okay. 00:06:31.000 --> 00:06:44.000 Please fill in your name as note taker two, three times this year, and then we are, you know, have that planned for and it's not something you as a convener need to kind of. 00:06:44.000 --> 00:06:48.000 ask us who can do the notes today. 00:06:48.000 --> 00:06:52.000 That sounds like a great plan. Let me add a note to our notes. 00:06:52.000 --> 00:06:59.000 Um, about that. A note to our notes. So. 00:06:59.000 --> 00:07:04.000 in the future. or I'll say. 00:07:04.000 --> 00:07:13.000 Please add your name to a few rows in the note taker column. 00:07:13.000 --> 00:07:22.000 And our calendar. And we can revisit that at our next meeting too and make sure we do. That would help a lot. Sometimes I try to do both, but there are many times where it's just not possible. 00:07:22.000 --> 00:07:27.000 Yeah. Yeah, well, we can help each other. It's… 00:07:27.000 --> 00:07:33.000 Yeah. That's a great, thank you for pointing it out. I had kind of forgotten about that call. 00:07:33.000 --> 00:07:44.000 Um… mentioned the discovery SIG. And maybe if we have time today, we can talk a little bit about that. I just wanted to check in one more time. 00:07:44.000 --> 00:07:50.000 I don't know exactly what our next steps should be with this document. 00:07:50.000 --> 00:08:08.000 I don't feel like we have everyone represented who typically attends Libris is missing from this. I know they're really busy right now. I don't know if… Like, EBSCO has… Any opinions on this, Alvaro, if like there are certain places you would not. 00:08:08.000 --> 00:08:14.000 advocate for your eyes or certain places you would like to use them. 00:08:14.000 --> 00:08:24.000 I know Stanford and Chair VD have filled this out, but I don't want to make assumptions for the whole group based on awesome. I know Tamika filled it out. 00:08:24.000 --> 00:08:29.000 And actually, Nancy, I see you're here now. Hi, I don't know if we're done. I think. 00:08:29.000 --> 00:08:31.000 I think we are, but. 00:08:31.000 --> 00:08:37.000 Oh, I wouldn't… I wanted to check about this. 00:08:37.000 --> 00:08:38.000 Yeah, for sure. 00:08:38.000 --> 00:08:41.000 Okay. 00:08:41.000 --> 00:08:42.000 Yeah, 00:08:42.000 --> 00:08:56.000 One thing we may be in. So, one thing we maybe could discuss in our group is where we envision it to be added in the UI. 00:08:56.000 --> 00:08:57.000 Mm-hmm. 00:08:57.000 --> 00:09:12.000 Because now, and probably the next 5, 8 years. It will only be libraries who are using linked data, who is really interested in. And as long as we don't have these. 00:09:12.000 --> 00:09:28.000 customizable display of the instance record. It probably will make most folio libraries annoyed if suddenly we have so many new data properties. 00:09:28.000 --> 00:09:40.000 in the so but but maybe so maybe we should start talk about. 00:09:40.000 --> 00:09:41.000 Mm-hmm. 00:09:41.000 --> 00:09:51.000 Where can we see it being posted in the UI for as a first phase solution for a solution longer term and. 00:09:51.000 --> 00:09:56.000 Third option could be when we finally have this customizable. 00:09:56.000 --> 00:10:02.000 view where each library can define. I want to see these properties. Don't want to see the rest. 00:10:02.000 --> 00:10:14.000 Yeah. Yeah, that's a great point. It came up with the instant source ID. There are some people like, well, if that's blank, then. 00:10:14.000 --> 00:10:18.000 I don't know, it didn't make sense for everyone. So that's a really great idea. 00:10:18.000 --> 00:10:30.000 Yeah, I mean, part of the instant source ID, too, is it made it so people who had macros and macro express had to redo all their macros. That was the, um, because it was an extra. 00:10:30.000 --> 00:10:33.000 tab set involved. 00:10:33.000 --> 00:10:41.000 Yeah. 00:10:41.000 --> 00:10:58.000 And then I think the next step could be to present it for the MMSIC because they are responsible for the inventory app. And of course we should, yeah. 00:10:58.000 --> 00:11:07.000 Maybe it would be a good idea to have Ryan Taylor informed before we we have a talk with Brian Taylor, who is the PO for. 00:11:07.000 --> 00:11:15.000 for inventory. 00:11:15.000 --> 00:11:22.000 That sounds good. Perhaps I will send one more message. 00:11:22.000 --> 00:11:34.000 to the slack asking if people are invested in this to fill it out, and if… If they don't, then I can just assume that they are… this is not a high priority for them, perhaps. 00:11:34.000 --> 00:11:41.000 Yeah, it would be really good to get Andreas to do it, though. 00:11:41.000 --> 00:11:42.000 Yep. 00:11:42.000 --> 00:11:43.000 Yeah. 00:11:43.000 --> 00:11:44.000 And, of course, all room. 00:11:44.000 --> 00:11:51.000 Yeah. Yeah, but but then tech, Andreas and the the ones who are active in our. 00:11:51.000 --> 00:12:01.000 I was sick if they can. fill it in, or give a reply that not not now. 00:12:01.000 --> 00:12:03.000 And Cornell, I see you're missing. That would be good. 00:12:03.000 --> 00:12:04.000 Oh, okay. 00:12:04.000 --> 00:12:12.000 I actually had… I had started, and then I realized that I'm not convinced we actually have use cases where we want. 00:12:12.000 --> 00:12:19.000 Your eyes, in the instance so I took us out, but gen… Jen, you and I should probably talk about this with 00:12:19.000 --> 00:12:29.000 with the… with a few colleagues, and I don't want it just to be my assumptions. 00:12:29.000 --> 00:12:37.000 That's great. And that's helpful to know too, if it's dropped off. 00:12:37.000 --> 00:12:38.000 There, because didn't you introduce it in the 1st place? 00:12:38.000 --> 00:12:39.000 a priority. 00:12:39.000 --> 00:12:48.000 I did because it was something that others were asking for. 00:12:48.000 --> 00:13:03.000 So, Kelly, you could maybe do a little action menu where we simply list all who has either decided to fill in or not fill in. So then you we can. 00:13:03.000 --> 00:13:07.000 Check it off, and then… It would be quick to see. 00:13:07.000 --> 00:13:11.000 Yeah. Oops. 00:13:11.000 --> 00:13:12.000 when all input. has been edited. 00:13:12.000 --> 00:13:15.000 Yeah, I want to say that, um, 00:13:15.000 --> 00:13:16.000 It's good that you, uh, talked with Ryan. 00:13:16.000 --> 00:13:19.000 Stop. 00:13:19.000 --> 00:13:23.000 Because, um, I listened to LinkedIn that I thought we are. 00:13:23.000 --> 00:13:27.000 naturally, we are using URIs for everything, so… 00:13:27.000 --> 00:13:29.000 Uh, I think he's the one. 00:13:29.000 --> 00:13:33.000 To make a… the call about… 00:13:33.000 --> 00:13:35.000 Inventory. 00:13:35.000 --> 00:13:38.000 In fact, we adapt. 00:13:38.000 --> 00:13:43.000 So, what is happening in inventory, so… 00:13:43.000 --> 00:13:44.000 Yeah. 00:13:44.000 --> 00:13:51.000 Okay. 00:13:51.000 --> 00:13:57.000 I would say, though. even those who are not filling it out. 00:13:57.000 --> 00:14:10.000 I think we should have a note whether they support this idea or not, even if they don't have a use case for their own particular institution at this time. 00:14:10.000 --> 00:14:13.000 Laura. 00:14:13.000 --> 00:14:18.000 I can only speak for myself, not Cornell right now. 00:14:18.000 --> 00:14:19.000 Yeah, I realize, but I mean… 00:14:19.000 --> 00:14:28.000 Um, so… so… but I'm assuming that we… we support it. I… I… I absolutely support it, I just don't want to prioritize 00:14:28.000 --> 00:14:33.000 Um, elements when I… we don't have any use cases. 00:14:33.000 --> 00:14:38.000 But if others have use cases, I absolutely support. 00:14:38.000 --> 00:14:45.000 Right? Okay. And I mean, it would be nice if Cornell could say that if you know. 00:14:45.000 --> 00:14:55.000 and others. I'm not meaning to stick it on you, but but it just seems, um… 00:14:55.000 --> 00:15:03.000 you know, because it is a sort of a major change to inventory in some ways that it would be nice to. 00:15:03.000 --> 00:15:14.000 know if… There are people who, you know, don't see themselves making use of it at this time, but… Understand the reasoning behind it and. 00:15:14.000 --> 00:15:29.000 Therefore, support. the ability of others to do so. 00:15:29.000 --> 00:15:40.000 Cool, that sounds good. And that's helpful. Thank you for thinking about. I just didn't want that doc to. 00:15:40.000 --> 00:15:50.000 vanish in relevance or or not be finished. Any other housekeeping items? 00:15:50.000 --> 00:15:58.000 Before we move into the settings page, and then we have a second item to talk about wolfComm Planning. 00:15:58.000 --> 00:16:02.000 Okay, so I just wanted to check in on this page. 00:16:02.000 --> 00:16:15.000 for… the linked tickets here in the title setting page requirements. I think we were good on the. 00:16:15.000 --> 00:16:24.000 fields being filled in for the most part. I do still see that Marva that is not blue core Marva is empty. 00:16:24.000 --> 00:16:33.000 Maybe that's fine. I don't know exactly who I might nudge to help fill that out, but I added screenshots for. 00:16:33.000 --> 00:16:42.000 The blue core editors and also Senopia, what we're calling Senopia Classic. 00:16:42.000 --> 00:16:47.000 There are screen dumps, I think, missing from. Everyone else. Yeah. So it. 00:16:47.000 --> 00:16:51.000 I will ask ours today, sorry. 00:16:51.000 --> 00:16:55.000 That's okay, no, no, go ahead. 00:16:55.000 --> 00:17:01.000 Oh, no, no, I just wanted to say that we, uh, I will add, uh, from the link data editor today. 00:17:01.000 --> 00:17:02.000 That's not the case. 00:17:02.000 --> 00:17:08.000 Okay, cool. Is there anything else you all need from us for this? 00:17:08.000 --> 00:17:15.000 Document except for the screenshots. 00:17:15.000 --> 00:17:27.000 No. Okay, awesome. Um… yeah, okay, cool. So I'm going to close that. And. 00:17:27.000 --> 00:17:46.000 So the new mockups you have shared, Alvaro. So I see there's still some labels missing. So in which we have in the spreadsheet. So it's not just a duplicate of instance source label, but also. 00:17:46.000 --> 00:17:50.000 We had some some more in in the settings page, if you. 00:17:50.000 --> 00:17:51.000 Okay, okay. 00:17:51.000 --> 00:17:52.000 We'll open it again. Yeah, okay, you will double check. Okay. 00:17:52.000 --> 00:17:55.000 Yeah, yeah, yeah, absolutely. 00:17:55.000 --> 00:17:56.000 I don't know, I will add it. 00:17:56.000 --> 00:17:59.000 Okay. Yeah. Okay, excellent. Thanks. 00:17:59.000 --> 00:18:09.000 Yes, please. 00:18:09.000 --> 00:18:26.000 Okay, great. Super. And then Nancy and I had started talking a little bit about wolfCom planning, and we saw Tiziana, your note that it's also on your mind. So… How do we feel about WolfCon this year? What? 00:18:26.000 --> 00:18:31.000 might we like to do? Um… Can I turn things over to you? 00:18:31.000 --> 00:18:42.000 Actually, I think I'd like to ask first who here has any possibility of going to WolfCon? 00:18:42.000 --> 00:18:43.000 So I hope I'm going that I asked today if I could get it a final confirmation from from Lynn, our CEO. 00:18:43.000 --> 00:18:53.000 implementing. 00:18:53.000 --> 00:18:55.000 I am going to… I'm going to ask… 00:18:55.000 --> 00:18:56.000 Okay. 00:18:56.000 --> 00:19:04.000 for, um, institutional support and offer to pay my travel fare myself and turn it into a… 00:19:04.000 --> 00:19:08.000 vacation afterward. So I am tentative. 00:19:08.000 --> 00:19:11.000 Because it is… 00:19:11.000 --> 00:19:15.000 It's complicated how it gets decided who can and can't go. 00:19:15.000 --> 00:19:16.000 Hmm. 00:19:16.000 --> 00:19:26.000 Well, yeah, trust me, it's complicated. Yes, I'm coming from the West Coast to Europe is also it's. 00:19:26.000 --> 00:19:43.000 It's doubly complicated. I'm hoping Kelly will be going. I think I probably will not. It's not like I don't think both of us can go, because I have other people that have to go. So. 00:19:43.000 --> 00:19:44.000 Hmm. 00:19:44.000 --> 00:19:50.000 I'll go to BitFrame in Europe. You know, that's sort of how. 00:19:50.000 --> 00:19:52.000 Um, Alvaro, are you going to be able to go? 00:19:52.000 --> 00:19:56.000 Yeah, I will possibly be going. 00:19:56.000 --> 00:19:57.000 Yeah. 00:19:57.000 --> 00:20:02.000 Yeah. Okay. Okay, I suspect Andreas will be there. 00:20:02.000 --> 00:20:18.000 Yeah, yeah, that's at least his plan. What I have heard. Andreas is also planning to do a presentation on Libris integration with folio. Now. 00:20:18.000 --> 00:20:30.000 They have, um… This is up and running. So so that presentation will be. 00:20:30.000 --> 00:20:34.000 probably partly also be framed. Relevant. 00:20:34.000 --> 00:20:40.000 Right. 00:20:40.000 --> 00:20:41.000 I want to be presenting, too. 00:20:41.000 --> 00:20:42.000 Great. 00:20:42.000 --> 00:20:44.000 Mm-hmm. 00:20:44.000 --> 00:20:46.000 About the link that I hit on, because… 00:20:46.000 --> 00:20:48.000 Okay. 00:20:48.000 --> 00:20:53.000 by then, we'll have the Trillium version complete, so… 00:20:53.000 --> 00:20:59.000 I don't need to present about that. 00:20:59.000 --> 00:21:00.000 Okay. 00:21:00.000 --> 00:21:09.000 Yeah, I saw your hand, Tiziano. I was pretty sure you were going to be going, but. 00:21:09.000 --> 00:21:15.000 You're going to have a very busy couple months in there. 00:21:15.000 --> 00:21:27.000 It's like all of the things that come up very close together this year. So it's. 00:21:27.000 --> 00:21:32.000 I mean, it's not like I wouldn't like to go to Prague, you know, but. 00:21:32.000 --> 00:21:39.000 I'm not sure we can pull that amount of funding itself. 00:21:39.000 --> 00:21:46.000 as I said, the problem is, if I go, I I prevent some of my staff from going, probably. So it's. 00:21:46.000 --> 00:21:53.000 you know, that's a trade off. Um… Um… 00:21:53.000 --> 00:21:58.000 I was thinking to go also because it's very close to Italy, Prague. So it's. 00:21:58.000 --> 00:22:02.000 Yeah, yeah, you can take the train, right? Yeah. 00:22:02.000 --> 00:22:19.000 So, perhaps not the train is easier to go with a plane, but anyway is very closed. And so yes, my integration was to go. But as company we we were asking. 00:22:19.000 --> 00:22:37.000 if it's good to join the meeting also in another way, for example, as sponsor, because they asked us. So it's for this reason that I underlined this topic in the agenda so that I can try to arrange. 00:22:37.000 --> 00:22:45.000 As a group, or I don't know, as a shared family in another. 00:22:45.000 --> 00:22:57.000 profile, but that is very easy for us this year. So we want to take the occasion of this so close event. 00:22:57.000 --> 00:23:06.000 I was in Prague last week with my daughter, and I have never been there before. It was such a lovely experience. 00:23:06.000 --> 00:23:07.000 Mm-hmm. 00:23:07.000 --> 00:23:11.000 Old, beautiful, very clean, very polite people. It's so awesome. So. 00:23:11.000 --> 00:23:15.000 Okay, okay, okay. 00:23:15.000 --> 00:23:17.000 you know, yeah, it's… Yeah. 00:23:17.000 --> 00:23:24.000 Well, at least I get to go to Barcelona. It's okay. 00:23:24.000 --> 00:23:27.000 We are trying to convince Nancy to come in Prague. 00:23:27.000 --> 00:23:32.000 Yeah. 00:23:32.000 --> 00:23:47.000 Well, you never know. That might turn up. But, um… Okay, so I mean, there there's sort of like there's a critical mass of people that are likely to be there. That's that's kind of. 00:23:47.000 --> 00:24:01.000 So it… Um… Do we want to have, you know, a sort of a working meeting or a. 00:24:01.000 --> 00:24:09.000 you know, brainstorming meeting there when we're actually people are actually in person, or. 00:24:09.000 --> 00:24:15.000 I don't… I think we're probably done with workshops for the moment until we have something further. 00:24:15.000 --> 00:24:23.000 My understanding is that working meetings are discouraged in general. 00:24:23.000 --> 00:24:27.000 Oh, okay. Hmm. 00:24:27.000 --> 00:24:53.000 So if our meeting could be at the end of the conference, it could be then kind of… you know, have a talk of all the individual presentations. And while everything are fresh in mind and inspired by all the new talk we could. 00:24:53.000 --> 00:25:11.000 you know, synthesize it in our context, and. Plan, what is follow-up? So it's… it's not, you know, work meeting, brainstorming, but it is kind of, you know. 00:25:11.000 --> 00:25:22.000 What does our sick make? make out of all of these new information and this brand new status on everything. 00:25:22.000 --> 00:25:24.000 Mm-hmm. 00:25:24.000 --> 00:25:38.000 Mm-hmm. But I mean, a lot of you would. All of you would be having to do some real work during the conference and make sure we get to a number of things. 00:25:38.000 --> 00:25:47.000 But, uh… It would make it good for your your application, Laura, because that can help you. 00:25:47.000 --> 00:25:50.000 that you really would be able to synthesize everything when you got back. 00:25:50.000 --> 00:25:56.000 Unfortunately, a lot of it comes down to who else is going. 00:25:56.000 --> 00:25:57.000 And… and the decision makers are people that, um, 00:25:57.000 --> 00:26:02.000 Yeah, I know, I know, trust me. 00:26:02.000 --> 00:26:12.000 Well, it's neither here nor there, but… 00:26:12.000 --> 00:26:18.000 I believe a panel style is one of the options in the proposal form. 00:26:18.000 --> 00:26:19.000 I got halfway through it starting something for us. And then I thought, I have no idea what I'm filling out yet, actually. 00:26:19.000 --> 00:26:29.000 We'll see. 00:26:29.000 --> 00:26:30.000 And the panel is nice. 00:26:30.000 --> 00:26:33.000 So that's a that's definitely an option. 00:26:33.000 --> 00:26:37.000 Um, if we have some people who are there in person and some who are 00:26:37.000 --> 00:26:44.000 remote, um, we could still have, I think, a productive panel. 00:26:44.000 --> 00:26:49.000 Yeah, last year that worked really well for the Blue Quora talk. 00:26:49.000 --> 00:26:53.000 Yeah, but it's nice to have them in person as much as possible. 00:26:53.000 --> 00:26:54.000 Mm-hmm. 00:26:54.000 --> 00:27:08.000 And I mean… the likelihood with the time zone difference, the likelihood of my being able to say, participate, say, might be low, just because the number of talks I'll have been able to get to. 00:27:08.000 --> 00:27:22.000 Will be greatly, uh… diminished, let's say. But that's okay. The rest of you can do it. 00:27:22.000 --> 00:27:27.000 Um… 00:27:27.000 --> 00:27:37.000 Who knows? Things might change. Anyhow, uh… 00:27:37.000 --> 00:27:43.000 Tiziana, does that help? If we do a panel discussion? Does that help you answer your question? 00:27:43.000 --> 00:27:59.000 Yes, sir. I was thinking, my interest is not to from my side to duplicate a presentation, for example. So not proposing something as. 00:27:59.000 --> 00:28:16.000 Chef family, so something that demo the editor in a session, and after having the meeting with our group. My interest is to have one presentation, one. 00:28:16.000 --> 00:28:25.000 effort that and I prefer to do something with you. So within the group, not as alone. 00:28:25.000 --> 00:28:26.000 Okay. 00:28:26.000 --> 00:28:27.000 Yeah. 00:28:27.000 --> 00:28:40.000 Okay, I think that makes a lot of sense. And I think if we have this panel like this about the conference synthesis, I think also it would be could start with sort of an overview. 00:28:40.000 --> 00:28:45.000 of what the linked open data, the SIG has been doing. 00:28:45.000 --> 00:28:53.000 And what it aims for, you know, kind of thing to, you know, to couch and then, you know, um. 00:28:53.000 --> 00:29:15.000 and maybe even, you know, just sort of a slight discussion of the difficulties of. 00:29:15.000 --> 00:29:16.000 Yeah. 00:29:16.000 --> 00:29:23.000 of… Um, you know… Integrating the markness of folio with linked data. And you know, I mean, the the problems we are trying to. We are. We are looking at. And then you know, then then sort of have a panel, and you know, okay. 00:29:23.000 --> 00:29:38.000 you know, how is the conference, you know, things going on at the conference? Is it, you know, helping or hindering us, or whatever kind of thing make it in terms of our group? Very much so, so we have a bit more of an identity, perhaps? 00:29:38.000 --> 00:29:39.000 Is that what you're thinking, Titiana, in a way? 00:29:39.000 --> 00:29:41.000 Yeah. 00:29:41.000 --> 00:30:01.000 Yes, yes, because in this way we can also have education to shortly demo something, no, or to speak about something. But from our side. But what is important, I think, is to underline as a group which kind of challenge we. 00:30:01.000 --> 00:30:17.000 kind of expectation we have to make better disintegration with polio. So not to stay focused on what, for example, JC at the wharf, how Jcricket works. But okay, we are doing something with ejectric and Folio. 00:30:17.000 --> 00:30:33.000 But which kind of challenges or additional problems we are having in going ahead with the new step to really realize this integration, this full integration? 00:30:33.000 --> 00:30:34.000 So speaking… 00:30:34.000 --> 00:30:41.000 Right. And and why we've been adding the wanting to add these things to inventory that are annoying people slightly. 00:30:41.000 --> 00:30:57.000 Exactly, exactly. So our experience could be just an example of what we are doing. But the focus should be on the group. So what we expect as group, why we are doing this. And so. 00:30:57.000 --> 00:31:06.000 More focus on the whole group. Even if each of them use the experience. 00:31:06.000 --> 00:31:08.000 Exactly. 00:31:08.000 --> 00:31:09.000 Now, now, Laura. 00:31:09.000 --> 00:31:14.000 I don't mean entirely, but I mean we need to be able… 00:31:14.000 --> 00:31:16.000 I'm happy as an equal alternative to Italy. 00:31:16.000 --> 00:31:25.000 An equal alternative, but we also need to be able to create an instance record with mark data, and then get the mark data out of there. 00:31:25.000 --> 00:31:29.000 And or overlay it with something that 00:31:29.000 --> 00:31:31.000 has a different source, you know? 00:31:31.000 --> 00:31:34.000 Exactly, it's not just for linked data. 00:31:34.000 --> 00:31:38.000 But it's one of many. 00:31:38.000 --> 00:31:39.000 Linked data is one of the reasons we need this. 00:31:39.000 --> 00:31:43.000 Hmm. 00:31:43.000 --> 00:31:46.000 And maybe we can find… maybe we can identify allies. 00:31:46.000 --> 00:31:49.000 portfolio to live up. portfolio to live up to its its own description. 00:31:49.000 --> 00:31:56.000 Yeah. 00:31:56.000 --> 00:32:01.000 Well, for it to live up to its own description as format neutral. 00:32:01.000 --> 00:32:03.000 Okay. And… 00:32:03.000 --> 00:32:05.000 There's some other details. 00:32:05.000 --> 00:32:07.000 like, hmm… 00:32:07.000 --> 00:32:09.000 For instance, um… 00:32:09.000 --> 00:32:15.000 In the editor, we plan this year to start implementing items and holdings. 00:32:15.000 --> 00:32:20.000 And that relates to users and circulation and orders. 00:32:20.000 --> 00:32:22.000 So, that's… 00:32:22.000 --> 00:32:24.000 Um, that… 00:32:24.000 --> 00:32:28.000 I guess that would involve a bigger discussion. 00:32:28.000 --> 00:32:31.000 for later, because… 00:32:31.000 --> 00:32:34.000 Um, how do we manage all that? 00:32:34.000 --> 00:32:39.000 We'll be using still XML internally? 00:32:39.000 --> 00:32:42.000 I don't know. 00:32:42.000 --> 00:32:45.000 That's something for the future, I guess. 00:32:45.000 --> 00:32:48.000 like, 6 months? 00:32:48.000 --> 00:32:49.000 Yeah. 00:32:49.000 --> 00:33:02.000 Yeah, that's a good topic idea. Expanded entities. as a challenge. Yeah. Or opportunity. We can decide how we want to frame everything. 00:33:02.000 --> 00:33:04.000 Or do maybe a little bit of both. 00:33:04.000 --> 00:33:05.000 Sorry, is it okay to ask for clarification? I heard holdings and items, but I'm not sure what it means in this context. 00:33:05.000 --> 00:33:10.000 Yeah, exactly. 00:33:10.000 --> 00:33:13.000 Like… 00:33:13.000 --> 00:33:17.000 Um, well, um… 00:33:17.000 --> 00:33:20.000 at least within the… within… 00:33:20.000 --> 00:33:22.000 Uh, the portfolio… 00:33:22.000 --> 00:33:24.000 Specifically, the linked data app. 00:33:24.000 --> 00:33:32.000 Um, so far, currently, um, it manages only works on instances, now it's… 00:33:32.000 --> 00:33:36.000 And, uh, it will be authorities. 00:33:36.000 --> 00:33:39.000 Very soon, but… 00:33:39.000 --> 00:33:41.000 Um… 00:33:41.000 --> 00:33:43.000 Later this year? 00:33:43.000 --> 00:33:45.000 like, the second half? 00:33:45.000 --> 00:33:48.000 We will start, uh… 00:33:48.000 --> 00:33:51.000 Um… 00:33:51.000 --> 00:33:56.000 exploring how to implement items and holdings, meaning, um, 00:33:56.000 --> 00:33:58.000 that if you… 00:33:58.000 --> 00:34:03.000 Uh, have a… an instance to have the… 00:34:03.000 --> 00:34:09.000 the physical version of the instance, like the, um, the actual item in your hand. 00:34:09.000 --> 00:34:13.000 With the barcode and all that. 00:34:13.000 --> 00:34:15.000 And, um, circulation information. 00:34:15.000 --> 00:34:18.000 Um… 00:34:18.000 --> 00:34:23.000 Managed by, uh, linked data. 00:34:23.000 --> 00:34:27.000 So, that's the item part and the holding part. 00:34:27.000 --> 00:34:28.000 is, um… 00:34:28.000 --> 00:34:32.000 Basically, the library, sub-library, or… 00:34:32.000 --> 00:34:35.000 the circulation unit… 00:34:35.000 --> 00:34:43.000 or the collection where that, uh, item belongs to. 00:34:43.000 --> 00:34:44.000 usually it's treated like a location. 00:34:44.000 --> 00:34:47.000 Okay, I get… I'm a noob, I didn't really realize that linked data 00:34:47.000 --> 00:34:52.000 would be involved with things like barcodes and stuff. 00:34:52.000 --> 00:34:55.000 Um, yeah, I mean… 00:34:55.000 --> 00:35:01.000 Uh, since we started implementing B-Prame, B-Prame also 00:35:01.000 --> 00:35:03.000 Uh… 00:35:03.000 --> 00:35:07.000 Uh, also takes care of that part. 00:35:07.000 --> 00:35:13.000 So, yeah, we're implementing the whole model. 00:35:13.000 --> 00:35:22.000 Yeah, I think this is just showing there's also we there are 2 different sort of models of doing it. 00:35:22.000 --> 00:35:23.000 True. 00:35:23.000 --> 00:35:31.000 And it's good to have both around, certainly to so. 00:35:31.000 --> 00:35:40.000 Um, so yeah, it's both both are possible. It's just there's 2 different choices about which way you go. So. 00:35:40.000 --> 00:35:42.000 Yeah, uh, sorry, Nosi. 00:35:42.000 --> 00:35:48.000 Yeah, I also been thinking about that, like, 00:35:48.000 --> 00:35:56.000 We're implementing one, but there should be a way to be able to use more than that. 00:35:56.000 --> 00:35:59.000 Uh… we don't have that solved. 00:35:59.000 --> 00:36:00.000 Yeah. 00:36:00.000 --> 00:36:07.000 Right. Right. And I mean, the big thing is to keep folio as flexible as possible while still working. 00:36:07.000 --> 00:36:21.000 Yeah. Yes. 00:36:21.000 --> 00:36:24.000 So it sounds like. 00:36:24.000 --> 00:36:34.000 Yeah, the panel could. I mean, yeah, I mean, we could also just, you know, talk a little bit about the the the different models of linked data that are that are. 00:36:34.000 --> 00:36:38.000 gelling in folio. Let's say. 00:36:38.000 --> 00:36:40.000 Mm-hmm. 00:36:40.000 --> 00:36:47.000 As part of the intro, and then… you know, we could have sort of a. 00:36:47.000 --> 00:36:54.000 that, and then the panel kind of thing, too. 00:36:54.000 --> 00:36:59.000 to make… to round, to keep it a round sort of meeting kind of thing. 00:36:59.000 --> 00:37:19.000 Yeah, I like this idea. In the previous years we've done very group centric insular work and sharing within each other, but oftentimes I feel like folks ask, Well, what's the link data? Sig working on? And this will be really nice opportunity for people in other Sigs to learn what we've been doing and the direction of the work. 00:37:19.000 --> 00:37:28.000 Give them a chance to ask questions and get excited, and maybe get some new participants, too. 00:37:28.000 --> 00:37:39.000 Sometimes things seem like old hat to me, like, oh, well, we've been talking about this for so long, but if you're not part of these groups, you may not know. 00:37:39.000 --> 00:37:50.000 all these different facets of of the work. 00:37:50.000 --> 00:37:54.000 So in our next meeting, should we start drafting? 00:37:54.000 --> 00:38:00.000 Does anyone know offhand the deadline? I think it's soon 20. 00:38:00.000 --> 00:38:01.000 Yeah. 00:38:01.000 --> 00:38:11.000 Yeah, it's March 25. So so next meeting. Oh, that would be the 17. So we're still in time. But yeah, we should. 00:38:11.000 --> 00:38:12.000 We should, uh, get it. 00:38:12.000 --> 00:38:13.000 Okay. 00:38:13.000 --> 00:38:19.000 Uh, perhaps we can share a Google Doc and we can start working together. 00:38:19.000 --> 00:38:20.000 Sounds great. 00:38:20.000 --> 00:38:28.000 Yeah. And but what we could do in a Google Doc could be maybe to post some of the previous texts. Then we have a little inspiration for. 00:38:28.000 --> 00:38:33.000 Yeah. 00:38:33.000 --> 00:38:35.000 Yeah. 00:38:35.000 --> 00:38:39.000 Yeah. 00:38:39.000 --> 00:38:47.000 Our next meeting. This is something I wanted to check. I have the 24th. It's the second Thursday. 00:38:47.000 --> 00:38:55.000 I'm sorry. The second Tuesday. I'm going to open up the doc so I have it in front of me. 00:38:55.000 --> 00:38:56.000 And the third… So it is the 17th? 00:38:56.000 --> 00:39:08.000 the 3rd Tuesday. No, it's the second Friday and the third Tuesday. 00:39:08.000 --> 00:39:09.000 Yeah, yeah. 00:39:09.000 --> 00:39:14.000 So we meet next on the 17th, actually. Okay. Darn, I'll update this. I thought we had more time. 00:39:14.000 --> 00:39:25.000 Okay. And I'll update the calendar too. Okay, great. That's actually better because it will be fresh in our minds. 00:39:25.000 --> 00:39:29.000 Would someone like to volunteer to make the dock, or I can start it? 00:39:29.000 --> 00:39:35.000 I can do that spreadsheet where we simply put in some previous text. And so, yeah, yeah, I can do that for us. 00:39:35.000 --> 00:39:49.000 Okay. Thank you, Charlotte. That's very helpful. Great. 00:39:49.000 --> 00:39:54.000 Well, I'll give you some input, Kelly. But I am, of course, I won't. 00:39:54.000 --> 00:39:58.000 be at the meeting, and it might be on the meeting on Tuesday. 00:39:58.000 --> 00:40:00.000 Oh, yes, I don't… Okay. 00:40:00.000 --> 00:40:07.000 I could be. I could be. We'll see. My plane is until 5 o'clock in the afternoon, so it's a… Beth. 00:40:07.000 --> 00:40:13.000 Okay. No pressure. 00:40:13.000 --> 00:40:14.000 Yeah, we could see if we could find some time. 00:40:14.000 --> 00:40:17.000 I might be running around a little, so… 00:40:17.000 --> 00:40:19.000 And if. 00:40:19.000 --> 00:40:24.000 Yeah. 00:40:24.000 --> 00:40:27.000 Cool. 00:40:27.000 --> 00:40:40.000 I'm trying to think if there's any other aspects of this conference piece. 00:40:40.000 --> 00:40:47.000 I think that sounds good. 00:40:47.000 --> 00:40:56.000 Are there any other topics or things? We should discuss today. 00:40:56.000 --> 00:40:59.000 Should we end a little early? 00:40:59.000 --> 00:41:05.000 Yes. 00:41:05.000 --> 00:41:06.000 Thank you. 00:41:06.000 --> 00:41:07.000 Yeah, so… Thank you. 00:41:07.000 --> 00:41:08.000 Okay, have a wonderful Friday! And or after Friday. 00:41:08.000 --> 00:41:09.000 You too. 00:41:09.000 --> 00:41:10.000 or end of Friday, or Friday evening to you, those of you there. 00:41:10.000 --> 00:41:11.000 Yeah, we… Yeah, we're… 00:41:11.000 --> 00:41:16.000 Yeah! Friday writ large. 00:41:16.000 --> 00:41:23.000 Hmm. See you, bye.