WEBVTT

00:23:33.000 --> 00:23:39.000
editors, integration pathways. It's almost like I want to say.

00:23:39.000 --> 00:23:47.000
Editors, community pathways. and.

00:23:47.000 --> 00:23:48.000
I like… I like that, yeah.

00:23:48.000 --> 00:23:52.000
implementation progress. Yeah.

00:23:52.000 --> 00:23:57.000
Sounds better. Yes.

00:23:57.000 --> 00:24:13.000
My soapbox is implementation. it's like we just have to get some implementation stuff off the ground.

00:24:13.000 --> 00:24:14.000
Maybe we can skip progress and then just end implementation.

00:24:14.000 --> 00:24:17.000
Cool.

00:24:17.000 --> 00:24:27.000
Yeah, yeah, I like that.

00:24:27.000 --> 00:24:28.000
Hmm?

00:24:28.000 --> 00:24:33.000
There's an interesting conversation that is just bubbling up.

00:24:33.000 --> 00:24:43.000
Yay, thanks, Jeremy. For Stanford internally. between our discovery team.

00:24:43.000 --> 00:24:49.000
and someone from EBSCO, not Alvaro. about the Linked Data app.

00:24:49.000 --> 00:25:03.000
And I mentioned. like having questions about build, and if we needed a build to bib frame mapping, and I know that's not here like as part of this, but it's just something I'm thinking of.

00:25:03.000 --> 00:25:19.000
Um. Because part of me wants to say bib frame implementation, but that's not necessarily true for every folio library either. So I guess we don't need to be that specific.

00:25:19.000 --> 00:25:23.000
No, it's probably better to be a bit vague there.

00:25:23.000 --> 00:25:27.000
Okay.

00:25:27.000 --> 00:25:34.000
Is… the other question I had for everyone is presenters. So.

00:25:34.000 --> 00:25:44.000
I think we talked about this in our last meeting of who was attending likely to attend, and and maybe we can talk about that again, and also who would be comfortable.

00:25:44.000 --> 00:25:55.000
listing themselves as a panelist or a co-presenter. I can submit it. I am… I put in my request to attend WolfCon in person. I have not been approved yet.

00:25:55.000 --> 00:26:02.000
Um, but it's likely that I'll go to WolfCon, and Nancy may not, but she may go to WolfCon.

00:26:02.000 --> 00:26:19.000
There's also the BidFrame Workshop in Europe. So we kind of have to be cognizant of all the different places we're supposed to be, and all the money we're asking for. And the fact that there's different amounts available. So.

00:26:19.000 --> 00:26:31.000
Is anyone comfortable or want to be on the panel or a facilitator of the panel, or comfortable listed as a presenter, and then we'll sort of figure out roles.

00:26:31.000 --> 00:26:39.000
after we're accepted, or once travel funding has been secured.

00:26:39.000 --> 00:26:40.000
Yay!

00:26:40.000 --> 00:26:48.000
I'm fine with that, I can be a panelist presenter, whatever I I expect to go not approved either, but we would be very surprised if… It was a problem.

00:26:48.000 --> 00:26:49.000
Okay.

00:26:49.000 --> 00:26:58.000
So, yeah.

00:26:58.000 --> 00:26:59.000
Okay.

00:26:59.000 --> 00:27:08.000
I will be there too, but I prefer to be in the panel, but not with a central role. So something that is not in organizing, but no, no, I can support the organization, of course, and present something, but not leading the panel if it's possible.

00:27:08.000 --> 00:27:20.000
Okay, thank you. Okay.

00:27:20.000 --> 00:27:21.000
Okay.

00:27:21.000 --> 00:27:27.000
And I think, Kelly, it's all fine. If you list yourself as so you submit, and you list yourself as the main presenter, even that you are have not gotten that final approval.

00:27:27.000 --> 00:27:28.000
Okay.

00:27:28.000 --> 00:27:32.000
I don't have neither, but I'm also acting like I'm coming. So, you know, we simply have to get things moving here.

00:27:32.000 --> 00:27:37.000
Okay.

00:27:37.000 --> 00:27:47.000
That's true. May I add your name, Charlotte, or would you rather not be on the panel or presenter?

00:27:47.000 --> 00:27:48.000
And I'm acting like I'm coming…

00:27:48.000 --> 00:27:49.000
Um, yeah, you can add my name, yeah. And we can figure out what to talk about.

00:27:49.000 --> 00:27:50.000
Oh, is there?

00:27:50.000 --> 00:27:58.000
I'm also acting like I'm coming, so you can put my name on, and Callie, if I am there, I'm happy to help

00:27:58.000 --> 00:28:00.000
To co-facilitate if that's helpful.

00:28:00.000 --> 00:28:01.000
Awesome. That would.

00:28:01.000 --> 00:28:06.000
I'm also happy to be the person who is keeping track of all the remote attendees and

00:28:06.000 --> 00:28:12.000
panelists, if I'm able to be there, which…

00:28:12.000 --> 00:28:13.000
I'm making a use for it.

00:28:13.000 --> 00:28:30.000
That would be great. That would be super helpful. Ld4 conference taught me so much. I thought initially, when I chaired that conference, oh, we don't need a we had 3 people facilitating every session, and I was like, that's so many people, but you have one person on the chat, one person on the slack.

00:28:30.000 --> 00:28:35.000
One person talking, it makes a world of a difference. It's so helpful.

00:28:35.000 --> 00:28:41.000
Yeah, I think the only way we can do hybrid…

00:28:41.000 --> 00:28:45.000
not… I won't even say well, but passively, is to have

00:28:45.000 --> 00:28:48.000
people really dedicated to…

00:28:48.000 --> 00:28:54.000
facilitating the interaction between those who are remote and those who are in person.

00:28:54.000 --> 00:29:02.000
Yeah.

00:29:02.000 --> 00:29:05.000
Anyone else?

00:29:05.000 --> 00:29:08.000
So now Alvaro is not here today, but we maybe should just check in with him if he, what his interest is.

00:29:08.000 --> 00:29:15.000
Yeah.

00:29:15.000 --> 00:29:23.000
I think I'm gonna be at Wolfcon Valley, so you could add me as presenter. I don't really want to facilitate.

00:29:23.000 --> 00:29:24.000
Mm-hmm.

00:29:24.000 --> 00:29:30.000
Okay. Great.

00:29:30.000 --> 00:29:32.000
I think Alvaro said he was. going and willing to do it. But I will double check, because you just.

00:29:32.000 --> 00:29:37.000
Going. Yeah, yeah. Yes, yes.

00:29:37.000 --> 00:29:38.000
Never want to add someone's name. Oh, great, Tamika.

00:29:38.000 --> 00:29:47.000
Uh, when is… is it this fall?

00:29:47.000 --> 00:29:48.000
Okay.

00:29:48.000 --> 00:30:00.000
Yes, it's in September. Let me see if I have a window? I have so many windows open. I'm just seeing if there's a chance. I already have it up. 2026.

00:30:00.000 --> 00:30:01.000
Okay.

00:30:01.000 --> 00:30:04.000
It's the first, yeah, it's the first week in September.

00:30:04.000 --> 00:30:11.000
So the pre-conference workshops are on August 31st, and then the conference itself is the first

00:30:11.000 --> 00:30:21.000
I think the first through the third?

00:30:21.000 --> 00:30:31.000
They are on Monday. Yeah, the pre-conference workshops are in person only, and on Monday, August 31st.

00:30:31.000 --> 00:30:32.000
But we are doing a regular session, right? Because I'm not going to the workshops, it's that has been.

00:30:32.000 --> 00:30:39.000
So, 1st through the 3rd. Yeah, and I…

00:30:39.000 --> 00:30:41.000
skipped for us. Mm-hmm.

00:30:41.000 --> 00:30:50.000
Yeah. I have reviewed this spreadsheet and found it or spreadsheet.

00:30:50.000 --> 00:31:11.000
slide deck, and found it very helpful. the form is also really great. I love the software they're using. I don't remember last year if it was the same or not, but I particularly love this year's submission form. I don't know whoever I should tell that to. It's so good. It's so easy.

00:31:11.000 --> 00:31:18.000
But I think I'm selecting this in-person hybrid. full panel.

00:31:18.000 --> 00:31:26.000
session. It's a little confusing. like. But I think this is the one we want.

00:31:26.000 --> 00:31:37.000
Would you all agree? I think this is because we don't want presenters virtual full, and we don't want short session, and we don't want a pre-conference workshop.

00:31:37.000 --> 00:31:38.000
I agree. Yeah, I agree. At least 50 min.

00:31:38.000 --> 00:31:43.000
Is this big enough? Yeah.

00:31:43.000 --> 00:31:46.000
Yeah, I agree to.

00:31:46.000 --> 00:31:47.000
Yeah, more than likely, I'll probably be, um, hybrid.

00:31:47.000 --> 00:31:50.000
Okay.

00:31:50.000 --> 00:31:51.000
But yeah.

00:31:51.000 --> 00:31:56.000
Okay. Great.

00:31:56.000 --> 00:32:01.000
And now figure out something to proceed if I have to.

00:32:01.000 --> 00:32:11.000
and we'll talk about it more like we'll plan typically how it's worked in the past, and I think it's worked really well. We've done a pre-conference.

00:32:11.000 --> 00:32:16.000
full day, I believe full day, both were full day, or the first year was a half day.

00:32:16.000 --> 00:32:31.000
But we talked about it leading up to the conference and and really figured out who was going to do what, and it was very cohesive, and I think they were really nice sessions, so there'll be support along the way. We won't just… The first step is really submitting this.

00:32:31.000 --> 00:32:47.000
getting accepted, and then we can circle back and figure out how we want to… Who wants to talk about what? What kind of questions we want to ask each other. So everyone can prepare and feel confident.

00:32:47.000 --> 00:32:53.000
Yay, great. Okay, so I'll try to do this this week. I think it's due on the 25th.

00:32:53.000 --> 00:33:12.000
and I I got halfway through the submission, and I thought, I'll see if it saves what I do, and lets me come back later. And it is, and it's emailing me. Remember your submission. So it's really great process. I need those reminders, and I'm glad it saved what I did, which was just enter my name, basically.

00:33:12.000 --> 00:33:13.000
Kelly, will you share the guidelines in the chat?

00:33:13.000 --> 00:33:17.000
Cool. Okay. Yeah. Yeah, yeah.

00:33:17.000 --> 00:33:20.000
The wolf can't. Yeah, yeah. The link to that. Cool.

00:33:20.000 --> 00:33:24.000
Let me go here.

00:33:24.000 --> 00:33:33.000
Yeah, I thought this was so great. And in slide format is also really nice because it's like visual, and you don't have to feel like you're reading an essay.

00:33:33.000 --> 00:33:47.000
I always appreciate. Love. the fact that anyone tells you what they're looking for is helpful. But this format I found particularly digestible.

00:33:47.000 --> 00:33:57.000
Okay. So with the remaining time, perhaps we can talk a little bit about the Discovery Sig meeting. So.

00:33:57.000 --> 00:34:08.000
The 21st will be a Tuesday. So it will be this time next month on the 21st April.

00:34:08.000 --> 00:34:23.000
Would it help if I read… The initial ask to the group. Okay, so let me open up my Slack and see if I can find the message.

00:34:23.000 --> 00:34:24.000
Okay.

00:34:24.000 --> 00:34:31.000
It was in our main channel initially, and then they… had just slide messaged me, or side messaged me. So, Nicole Trujillo from.

00:34:31.000 --> 00:34:45.000
The Discovery Sig writes, EBSCO has been testing out some linked data elements in discovery like author pages and sites cited by. We are reaching out to them to see if they would like to discuss these features in further detail, and we'll let you know what we hear.

00:34:45.000 --> 00:35:04.000
We were also wondering if the linked data SIG is interested in having a discussion sometime this summer. So we're meeting a little sooner than that, I guess, depending on where you are, about the development of the linked data app in Folio and the various ways it might impact user resource discovery.

00:35:04.000 --> 00:35:05.000
I know I haven't been keeping up with the app development. I'm very interested.

00:35:05.000 --> 00:35:13.000
keeping up with the outcome, and then…

00:35:13.000 --> 00:35:14.000
I'm sorry I'm late, eh?

00:35:14.000 --> 00:35:15.000
Hi, Alvaro.

00:35:15.000 --> 00:35:17.000
I'm just a meeting.

00:35:17.000 --> 00:35:21.000
Like, what's changed our last, uh, at last hour, so…

00:35:21.000 --> 00:35:22.000
Thank you. Thank you.

00:35:22.000 --> 00:35:39.000
That's okay. Welcome. We're just talking about the Discovery Sig that wants to meet with us on April 21st. The date has changed. And so I was just reading what Nicole had written to us.

00:35:39.000 --> 00:35:47.000
Nicole is at the University of Colorado Boulder, which I believe our former co-convener, Chris Long was there, right?

00:35:47.000 --> 00:35:49.000
Yes.

00:35:49.000 --> 00:35:57.000
Yeah, so that's great. It'll be nice to have someone from Boulder back in the group, even if temporarily. So.

00:35:57.000 --> 00:36:06.000
Yeah. What do you all think? Had you heard about this? I I hadn't heard about this. The author cards.

00:36:06.000 --> 00:36:07.000
Did she say what environment?

00:36:07.000 --> 00:36:13.000
That was? Was that EDS? Is that LOCATE?

00:36:13.000 --> 00:36:16.000
Because my first thought, honestly, was, well, that's…

00:36:16.000 --> 00:36:20.000
Similar to something that we do at Cornell and Blacklight.

00:36:20.000 --> 00:36:24.000
Not the cards, but the… well, yeah, kind of a card.

00:36:24.000 --> 00:36:27.000
For authors pulling… pulling from various

00:36:27.000 --> 00:36:34.000
Sources.

00:36:34.000 --> 00:36:38.000
I did not say. Alvar, do you know?

00:36:38.000 --> 00:36:40.000
No.

00:36:40.000 --> 00:36:44.000
where the author cards? Is it… What platform?

00:36:44.000 --> 00:36:47.000
I see.

00:36:47.000 --> 00:36:54.000
You know, I should… I should know if it's… we actually use EDS for our e-resources.

00:36:54.000 --> 00:36:58.000
Um, we use Blacklight for our…

00:36:58.000 --> 00:37:02.000
Our catalog data, but we have EDS implemented, so I should be able to look at our EDSs.

00:37:02.000 --> 00:37:04.000
Uh, I know…

00:37:04.000 --> 00:37:09.000
I know that it is, yeah, I have something called a scholarly graph.

00:37:09.000 --> 00:37:13.000
And, um, I don't know, because I…

00:37:13.000 --> 00:37:17.000
And kind of… it's not my area, but uh…

00:37:17.000 --> 00:37:24.000
I know they use a knowledge graph, and they have, um, information about authors.

00:37:24.000 --> 00:37:28.000
So, maybe that's it.

00:37:28.000 --> 00:37:31.000
Yeah, they… they… they display…

00:37:31.000 --> 00:37:33.000
I don't know how they… they…

00:37:33.000 --> 00:37:39.000
make it, but they make a small knowledge graph.

00:37:39.000 --> 00:37:42.000
for the author. That's what I know about it.

00:37:42.000 --> 00:37:45.000
Yeah, exactly, it's go on the graph.

00:37:45.000 --> 00:37:54.000
Maybe that's what they mean by other card.

00:37:54.000 --> 00:37:55.000
Yeah, that's the name I heard, people pages.

00:37:55.000 --> 00:38:00.000
Yeah, that's possible people pages.

00:38:00.000 --> 00:38:06.000
That would be very interesting.

00:38:06.000 --> 00:38:15.000
Because a question I had, I did hear about this, and one question I had about this. It didn't seem like people could edit.

00:38:15.000 --> 00:38:20.000
the data that's being used for this graph that it's.

00:38:20.000 --> 00:38:21.000
Yeah,

00:38:21.000 --> 00:38:32.000
the… I was confused if this was a product or not. Like, is this something you would subscribe to, and then the data would be used in those features, or is this something that.

00:38:32.000 --> 00:38:42.000
Libraries would have. the ability to edit if there were issues like in the open Alex data or the Crossref data or maybe EBSCO is doing cleaning.

00:38:42.000 --> 00:38:46.000
Oh, what?

00:38:46.000 --> 00:38:47.000
I don't know how open it is, I'm not sure.

00:38:47.000 --> 00:38:49.000
That's a little off topic.

00:38:49.000 --> 00:38:52.000
I know it exists, but I never took the…

00:38:52.000 --> 00:38:57.000
The dental research on that. But, um…

00:38:57.000 --> 00:39:03.000
I will have to, too, because I will have… we'll start developing, um, authorities.

00:39:03.000 --> 00:39:08.000
Authority, I think capabilities starting on June.

00:39:08.000 --> 00:39:10.000
And, uh, let's…

00:39:10.000 --> 00:39:13.000
people. So…

00:39:13.000 --> 00:39:17.000
Uh, um, yeah, and that's… that's something I had, like…

00:39:17.000 --> 00:39:20.000
in my schedule.

00:39:20.000 --> 00:39:23.000
Uh, after, uh, Trillium…

00:39:23.000 --> 00:39:27.000
is released to check on that.

00:39:27.000 --> 00:39:29.000
like, uh, how we can, uh, edit

00:39:29.000 --> 00:39:31.000
Hmm.

00:39:31.000 --> 00:39:33.000
people from external sources.

00:39:33.000 --> 00:39:36.000
I don't have an idea.

00:39:36.000 --> 00:39:38.000
And also, I think that, um,

00:39:38.000 --> 00:39:42.000
this thing about, uh, external…

00:39:42.000 --> 00:39:46.000
Uh, editors or external tools might be useful.

00:39:46.000 --> 00:39:51.000
But the, uh… that's, uh…

00:39:51.000 --> 00:39:55.000
It's more like a feeling, you know, because I hadn't made the research.

00:39:55.000 --> 00:39:56.000
But the… but we are going that way, at least.

00:39:56.000 --> 00:39:59.000
Yeah.

00:39:59.000 --> 00:40:02.000
the… with the anecdote.

00:40:02.000 --> 00:40:04.000
Um, because authoritious people.

00:40:04.000 --> 00:40:19.000
So it sounds. Yeah. So it sounds like it could be. It could be many things. It could be the use of that authority data.

00:40:19.000 --> 00:40:20.000
Yeah.

00:40:20.000 --> 00:40:29.000
in folio. It could be the scholarly graph. So we need to ask her and confirm where, and my second question, Alvaro is, can you show us that in the future, in the near future? Maybe in like May?

00:40:29.000 --> 00:40:30.000
Oh…

00:40:30.000 --> 00:40:33.000
the authorities for people like data. Can you show us that soon?

00:40:33.000 --> 00:40:38.000
Oh, I think that…

00:40:38.000 --> 00:40:44.000
We start actual development on June, so I guess I could choose something

00:40:44.000 --> 00:40:45.000
In July.

00:40:45.000 --> 00:40:46.000
Oh. Okay, that would be great.

00:40:46.000 --> 00:40:50.000
That would be the…

00:40:50.000 --> 00:40:53.000
Yeah.

00:40:53.000 --> 00:40:54.000
Well, yeah.

00:40:54.000 --> 00:40:55.000
Yeah, whenever you're ready. I'm sorry, I misunderstood and thought it would be ready in June, but you're saying the development's going to start in June.

00:40:55.000 --> 00:40:57.000
Yeah.

00:40:57.000 --> 00:40:58.000
Yeah, we… we're just, uh…

00:40:58.000 --> 00:41:01.000
Okay. Awesome.

00:41:01.000 --> 00:41:04.000
We are starting a static planning.

00:41:04.000 --> 00:41:06.000
Like, like Squeak, we started.

00:41:06.000 --> 00:41:20.000
Okay. Okay.

00:41:20.000 --> 00:41:22.000
Own!

00:41:22.000 --> 00:41:27.000
Oh, um…

00:41:27.000 --> 00:41:28.000
Awesome, awesome.

00:41:28.000 --> 00:41:30.000
Are there issues we can follow? I'm just very curious about it, because that's my primary role at Stanford. I'm authorities and entity management. So this is like my sweet spot. If you if you have any Jira issues, just as a personal, I would love to see them when you're ready, or when they come together.

00:41:30.000 --> 00:41:33.000
Yeah, yeah. I will make… I will ask you…

00:41:33.000 --> 00:41:34.000
Yeah, for sure, because…

00:41:34.000 --> 00:41:35.000
Um, okay. Okay. Thank you.

00:41:35.000 --> 00:41:40.000
Uh, I'm sure, uh, we will bump into a lot of…

00:41:40.000 --> 00:41:43.000
issues, um…

00:41:43.000 --> 00:41:48.000
Yeah, and uh… also, I'm wondering…

00:41:48.000 --> 00:41:53.000
I don't know also how to manage that, but uh…

00:41:53.000 --> 00:41:56.000
That relates with external, like, ontologies.

00:41:56.000 --> 00:42:01.000
or vocabularies outside the different.

00:42:01.000 --> 00:42:04.000
So…

00:42:04.000 --> 00:42:06.000
Yeah, I still don't know also how to handle that.

00:42:06.000 --> 00:42:08.000
But, uh, yeah, I will… I will reach out to you.

00:42:08.000 --> 00:42:23.000
Yeah. I would love that. I've been thinking about these things, but I have known… I mean, I'm talking about it, but to know you're working on it is very helpful.

00:42:23.000 --> 00:42:24.000
Exactly.

00:42:24.000 --> 00:42:32.000
Because, yeah, MAD's Rdf, for example, instead of yeah, yeah. Cool. Okay, so.

00:42:32.000 --> 00:42:38.000
I don't know where that leaves us. So we have one question about where the actual cards are going.

00:42:38.000 --> 00:42:42.000
like, what… what the actual project is. But are there things that we want to.

00:42:42.000 --> 00:42:52.000
communicate to them that we're hoping for. I mean, we've talked about discovery in this group before.

00:42:52.000 --> 00:42:56.000
Well, uh…

00:42:56.000 --> 00:42:59.000
from the perspective, it…

00:42:59.000 --> 00:43:01.000
It has to do with the UI.

00:43:01.000 --> 00:43:04.000
How we communicate with the UI.

00:43:04.000 --> 00:43:07.000
And how, um…

00:43:07.000 --> 00:43:09.000
Um, data can be…

00:43:09.000 --> 00:43:12.000
actually shared.

00:43:12.000 --> 00:43:16.000
Um…

00:43:16.000 --> 00:43:20.000
I know that we need, uh, to open the… the graph.

00:43:20.000 --> 00:43:22.000
We still don't?

00:43:22.000 --> 00:43:28.000
Uh, but, um, I guess that there should be expectations.

00:43:28.000 --> 00:43:31.000
from the discovery sick.

00:43:31.000 --> 00:43:38.000
like, uh, what information they expect to have, or to have access to.

00:43:38.000 --> 00:43:41.000
Like, um, um…

00:43:41.000 --> 00:43:44.000
Are they, like, expecting, like, a…

00:43:44.000 --> 00:43:49.000
full nodes to be open, uh…

00:43:49.000 --> 00:43:54.000
what format are they expecting to be stuffed in?

00:43:54.000 --> 00:43:59.000
Like, are they expecting something like, um, what, uh, Library of Congress has?

00:43:59.000 --> 00:44:03.000
Like, or something like BF has?

00:44:03.000 --> 00:44:05.000
It's, like, small links at the end.

00:44:05.000 --> 00:44:09.000
Um, I don't know. That kind of stuff could be interesting.

00:44:09.000 --> 00:44:18.000
No.

00:44:18.000 --> 00:44:22.000
Yeah, I agree. The nuts and bolts of what they actually would use and how to get access.

00:44:22.000 --> 00:44:29.000
Yeah. Exactly.

00:44:29.000 --> 00:44:31.000
True, yeah, APIs.

00:44:31.000 --> 00:44:32.000
Exactly.

00:44:32.000 --> 00:44:42.000
I'm thinking about Apis. I don't know why.

00:44:42.000 --> 00:44:48.000
Yeah, what, like, properties they are expecting to fetch, or classes?

00:44:48.000 --> 00:44:50.000
And, uh…

00:44:50.000 --> 00:44:57.000
Are they thinking just, uh, VFrame? Are they thinking RDI registry?

00:44:57.000 --> 00:45:00.000
Or something else?

00:45:00.000 --> 00:45:05.000
It's relevant to it.

00:45:05.000 --> 00:45:15.000
Does anyone know if the Discovery SIG is like our SIG in that they have multiple ways of doing discovery, but they all.

00:45:15.000 --> 00:45:37.000
semi-seek similar things, or are they rallied around a particular discovery tool or platform, like viewfind or Blacklight, or is it a it sounded in the past to me like a mix?

00:45:37.000 --> 00:45:41.000
Okay, Jen says multiple. Thank you.

00:45:41.000 --> 00:45:48.000
Well, anything to do with with discovery is basically indexing. How would you?

00:45:48.000 --> 00:45:59.000
How would you index things so that the discovery tool would make sense of the linked data, no matter what type of it you have, you need to index it somehow.

00:45:59.000 --> 00:46:06.000
To mix it to whichever search engine the discovery.

00:46:06.000 --> 00:46:15.000
Solution users. I'm sure there's… plenty of knowledge about how to make.

00:46:15.000 --> 00:46:35.000
graph data flattened out into an index. Um, we do it, ShareVD does it sure there's a lot of others, but but there's no currently no one. Any one of the the current discovery solutions that can index that.

00:46:35.000 --> 00:46:51.000
And so that would be… my perspective. One of the first things, how can we get one of them, at least anyone to try an index something.

00:46:51.000 --> 00:47:01.000
Some variety of frame or some other version of linked data and and see how that would work out, basically.

00:47:01.000 --> 00:47:02.000
Could we find our black light, or it could be EDS, or it could be something else.

00:47:02.000 --> 00:47:07.000
See if that's there.

00:47:07.000 --> 00:47:09.000
Yeah.

00:47:09.000 --> 00:47:16.000
That is something we are very interested in at Cornell, thinking about trying to move toward

00:47:16.000 --> 00:47:18.000
production, because we…

00:47:18.000 --> 00:47:31.000
We don't want to create, like, bib frame to convert to mark.

00:47:31.000 --> 00:47:36.000
It feels like a chicken-egg.

00:47:36.000 --> 00:47:42.000
Situation.

00:47:42.000 --> 00:47:47.000
Tizian, I see your hand. I was hoping you might say something.

00:47:47.000 --> 00:48:03.000
I was… I'm sorry, because I'm sick, so this is an additional issue. I was thinking to what Andreas was saying, and this comes to my mind the fact that.

00:48:03.000 --> 00:48:20.000
With index data, we are managing a pilot project for Palci network, Palci consortium. And within this pilot, we also have.

00:48:20.000 --> 00:48:38.000
An integration between entities produced using the LOD platform, so the share family components and we find. So it could be an interesting mix, and this could be an interesting test.

00:48:38.000 --> 00:48:54.000
Uh, about how these two components, one that is originally focused on entity that is shared, and the second one that is originally focused on record that is buffet can work together.

00:48:54.000 --> 00:49:03.000
So I think that at a certain time we can, I hope that we can demo something or discuss about this, the result of this.

00:49:03.000 --> 00:49:08.000
That would be amazing. I would love to see that because my mind went to.

00:49:08.000 --> 00:49:16.000
the discussions I've heard in 2 2 places, the blue core discussions around indexing bid frame, but also.

00:49:16.000 --> 00:49:25.000
the MMSIG talking about indexing mark. And how those two will interact.

00:49:25.000 --> 00:49:42.000
and I was thinking more on the back end, but the front, the discovery aspect is… is exactly the same type of thing. So I would love to see that. That would be great. And I'm sure the discovery Sig would too be if they haven't already seen it, because that's such a great.

00:49:42.000 --> 00:49:56.000
intersection of our interests. That's so cool. Thank you.

00:49:56.000 --> 00:50:03.000
Okay, so we have about 10 minutes left. It sounds like.

00:50:03.000 --> 00:50:21.000
I I will look through our notes and this recording and make sure that the questions we have for them and the comments are kind of captured in advance, so we can review them next week before we meet with them on the 21st, and if there's anything we should gather, like any.

00:50:21.000 --> 00:50:29.000
thing we can share with them. Relative links. I will look and see if I have anything.

00:50:29.000 --> 00:50:46.000
I don't know if I do, and I don't want to front-load it too much, like, whatever kind of organic conversation we have, there may be new things that surface, but… Clarity on… where this discovery, these discovery enhancements are happening.

00:50:46.000 --> 00:50:55.000
What kind of data they're working with? What kind of data they want to work with, and is it what we're making? Is it what we're indexing?

00:50:55.000 --> 00:51:11.000
And what kinds of experiments or pilots or current work is being done by this group in the area of discovery that might be relevant. I've seen other Sigs do like crossover presentations and demos. So maybe.

00:51:11.000 --> 00:51:16.000
We could get together for something like that with them. Um, so we can see the viewfind and the share.

00:51:16.000 --> 00:51:22.000
together. That might be kind of a cool thing to do. And so you don't have to do it twice.

00:51:22.000 --> 00:51:25.000
But I don't know, if there's other things that come to mind.

00:51:25.000 --> 00:51:38.000
We can keep adding to our list. But that sounds like it'll be a really good discussion.

00:51:38.000 --> 00:51:44.000
Andreas, are you all indexing the already? Do you have a.

00:51:44.000 --> 00:51:56.000
I'm thinking back to a presentation I saw at the Bibframe workshop in Europe last year. That was pretty, I think they had just talked about types, content types in the discovery interface.

00:51:56.000 --> 00:52:03.000
Yeah, uh, we index. We use Elasticsearch for most of our.

00:52:03.000 --> 00:52:05.000
Hmm.

00:52:05.000 --> 00:52:12.000
Front end are both cataloging editor and the front ends, but it's basically the same.

00:52:12.000 --> 00:52:30.000
Search index for. for both of them. So we do a lot of stuff there to make it presentable, but it's… basically flattening out the linked data into regular JSON to be able to be read by Elasticsearch.

00:52:30.000 --> 00:52:44.000
And currently, the last I've heard about it was trying to decrease the size of the indexes because we… index the same things over and over in some ways.

00:52:44.000 --> 00:52:49.000
So we're looking at making that smaller. But that's details.

00:52:49.000 --> 00:52:57.000
Um, not my area of expertise per se, but can probably find out more and.

00:52:57.000 --> 00:53:00.000
to have something to talk about when we meet then.

00:53:00.000 --> 00:53:06.000
That would be really helpful, and we… we have Elasticsearch in Sunopia.

00:53:06.000 --> 00:53:18.000
we're calling it Senopia Classic. I don't know if we could keep doing that, but the Senopia that currently exists outside of Blue Core. Maybe Jeremy, we could share some stuff about what we're doing with the blue core.

00:53:18.000 --> 00:53:21.000
Database.

00:53:21.000 --> 00:53:31.000
Sure. I mean, we're using sort of Postgres has really improved its searching and full pack searching, particularly with JSON objects.

00:53:31.000 --> 00:53:34.000
So in Blue Core, instead of having a separate.

00:53:34.000 --> 00:53:44.000
Uh, search layer with its own stack. We've, uh, we've been using and having some success with using Postgres.

00:53:44.000 --> 00:53:51.000
Um, and it's indexing, so… But yeah, I'd be happy to talk about that.

00:53:51.000 --> 00:53:56.000
That would be great, especially as we gear up to make change, like, get it to the Mvp State. That would be really cool.

00:53:56.000 --> 00:53:58.000
Yeah, yeah, for sure.

00:53:58.000 --> 00:54:07.000
That'd be very interesting to hear about. So we both have Postgres and Elasticsearch index. What's what? And then we have sparkle on the side. And yeah.

00:54:07.000 --> 00:54:11.000
Yeah.

00:54:11.000 --> 00:54:12.000
Yeah.

00:54:12.000 --> 00:54:16.000
So it's like we're where does the data actually live? Yeah.

00:54:16.000 --> 00:54:32.000
And this is the same for our architecture because also we have Postgres, Solar or Elasticsearch and the Triple Store. And I think that also the Labor Congress has the same architecture.

00:54:32.000 --> 00:54:38.000
Yeah. Yeah, I think that's that's true.

00:54:38.000 --> 00:54:43.000
Great. Okay, so to be continued.

00:54:43.000 --> 00:54:48.000
Um, so… So I will submit.

00:54:48.000 --> 00:54:56.000
Our proposal. Thank you so much for your contributions to that. And then our next meeting will be on April 10th.

00:54:56.000 --> 00:55:05.000
which is a Friday. 7am Pacific, 10 am. Eastern. Hopefully that time zone converter works.

00:55:05.000 --> 00:55:13.000
Um… I need to get in the habit of having Utc or.

00:55:13.000 --> 00:55:17.000
European Central Time, something a third, but my brain.

00:55:17.000 --> 00:55:23.000
It's at its limits. Not that that's a good excuse.

00:55:23.000 --> 00:55:33.000
But I think that's all for today, unless there's any other comments or… Questions?

00:55:33.000 --> 00:55:40.000
Okay, awesome. Thank you so much. We'll see you next month, and we'll be in touch in Slack if anything comes up.

00:55:40.000 --> 00:55:43.000
See you. Bye-bye.

00:55:43.000 --> 00:55:44.000
Hi, thank you.

00:55:44.000 --> 00:55:48.000
Okay.

00:55:48.000 --> 00:55:49.000
Oh, yeah. Thank you, Charlotte. Yeah, Alvaro.

00:55:49.000 --> 00:55:55.000
Oh, before you leave, all of you now, Alvaro is here. So we could ask about attending the Wolfcon, then we… Maybe if you pull up the notes, I have put in that question mark in the notes and then we can add it.

00:55:55.000 --> 00:55:59.000
Oh, great. Um, Alvaro, I think you said this.

00:55:59.000 --> 00:56:02.000
you have to refresh, yeah.

00:56:02.000 --> 00:56:14.000
Yeah, yeah, I think you confirmed this the last time we met, but just to double check. May we list you as a panelist and a presenter for our WolfCon presentation?

00:56:14.000 --> 00:56:16.000
Yes, yes, please. Uh, I have back.

00:56:16.000 --> 00:56:17.000
80% of certainty that I will be.

00:56:17.000 --> 00:56:19.000
Okay.

00:56:19.000 --> 00:56:22.000
Going.

00:56:22.000 --> 00:56:25.000
Okay, great. That'll be wonderful. Thank you so much.

00:56:25.000 --> 00:56:27.000
Thank you.

00:56:27.000 --> 00:56:30.000
Okay.

00:56:30.000 --> 00:56:31.000
Thank you. Goodbye.

00:56:31.000 --> 00:56:43.000
Thank you. Bye.

