WEBVTT 1 00:01:12.900 --> 00:01:14.460 Sharon Markus: Hey, everybody! 2 00:01:15.090 --> 00:01:17.650 Sharon Markus: Welcome, we'll get started shortly! 3 00:02:34.990 --> 00:02:36.190 Scott Perry (UChicago): Good morning. 4 00:02:37.740 --> 00:02:41.910 Scott Perry (UChicago): Give it another minute for… People show up. 5 00:02:45.240 --> 00:02:45.930 Sharon Markus: Hello! 6 00:03:27.850 --> 00:03:34.730 Scott Perry (UChicago): It looks like we slowed down. Let's go ahead and get started. Is there someone who'd like to take attendance, or… 7 00:03:34.890 --> 00:03:36.840 Scott Perry (UChicago): I can do it. 8 00:03:36.840 --> 00:03:37.909 Sharon Markus: I can do that. 9 00:03:37.910 --> 00:03:43.910 Scott Perry (UChicago): I think you'll be talking in a few minutes a lot, too, so I can do that, if you'd like. 10 00:03:45.250 --> 00:03:48.839 Scott Perry (UChicago): Let me just… Go back to the agenda. 11 00:03:54.690 --> 00:03:57.839 Scott Perry (UChicago): Sorry for the late announcement of the meeting, I… 12 00:03:59.220 --> 00:04:07.810 Scott Perry (UChicago): the change to three Mondays has upset my schedule, so… in terms of when I'm convening. 13 00:04:10.940 --> 00:04:18.449 Scott Perry (UChicago): But… and… let's see… Are there any new members today? I don't think so. 14 00:04:27.720 --> 00:04:28.550 Scott Perry (UChicago): Nerd. 15 00:04:29.580 --> 00:04:35.019 Scott Perry (UChicago): Definitely looking for people to work with us on derived tables support. 16 00:04:35.350 --> 00:04:39.289 Scott Perry (UChicago): And, please let us know if you'd like to do that. 17 00:04:44.490 --> 00:04:48.769 Scott Perry (UChicago): And, Sharon, would you like to start the update on MetaDB? 18 00:04:48.910 --> 00:04:50.740 Scott Perry (UChicago): Data Privacy Subgroup? 19 00:04:52.940 --> 00:04:57.290 Sharon Markus: Sure. I suppose in, a little bit of attendance. 20 00:04:57.290 --> 00:04:58.269 Scott Perry (UChicago): No, I can do that. 21 00:04:58.290 --> 00:05:00.769 Sharon Markus: I'll let you do the rest. 22 00:05:00.940 --> 00:05:02.909 Scott Perry (UChicago): Thanks, that's what I was saying. 23 00:05:02.910 --> 00:05:07.230 Sharon Markus: Alright, let me just share my screen. 24 00:05:15.910 --> 00:05:16.780 Sharon Markus: Let's do… 25 00:05:22.490 --> 00:05:37.499 Sharon Markus: Okay, so we have a couple links for this in the Reporting SIG agenda. If you want to take a look at this later, we have this presentation, which is just a summary of what's been going on in the MetaDB data privacy subgroup. 26 00:05:37.620 --> 00:05:49.160 Sharon Markus: Of this reporting sig. And, we have, the notes from the meetings, which have a lot of details, so… but if you're interested in… 27 00:05:49.210 --> 00:06:05.259 Sharon Markus: JIRA links and other information, that's all there. Also, I'm going to just open this up to other folks who are members of the data privacy subgroup to jump in and add anything I'm missing. 28 00:06:05.260 --> 00:06:13.359 Sharon Markus: As we go. Lauren, has been working really hard to take our, Lauren Sini 29 00:06:13.360 --> 00:06:29.519 Sharon Markus: our PO, to take the feedback from, this work over to index data and working with developers directly on that. So, Lauren, in particular, you may have things to, to, say as we go through this information. 30 00:06:30.280 --> 00:06:32.910 Sharon Markus: And I invite you to do that. 31 00:06:33.150 --> 00:06:41.430 Sharon Markus: All right, so just for a summary of what the group has been working on, our areas of focus have been… 32 00:06:41.920 --> 00:06:43.909 Sharon Markus: Can everybody see this okay? 33 00:06:47.760 --> 00:06:49.270 Sharon Markus: Can you all see? 34 00:06:49.270 --> 00:06:50.140 Ann Crowley: Yes. 35 00:06:50.140 --> 00:06:52.310 Sharon Markus: My… okay, thank you. 36 00:06:52.800 --> 00:06:59.689 Sharon Markus: All right, and can you hear me okay? I, you know, actually, I don't know if I have my audio quite right. I don't think I do, no, I… 37 00:07:00.570 --> 00:07:03.430 Sharon Markus: Don't. Just a sec here. 38 00:07:03.840 --> 00:07:06.810 Sharon Markus: There we go, this probably just got a lot better. 39 00:07:07.120 --> 00:07:10.230 Sharon Markus: Yeah, okay. 40 00:07:10.620 --> 00:07:28.909 Sharon Markus: Okay, so the areas of focus for the MetaDB Data Privacy Subgroup. We've been talking a lot about reporting app permissions, roles, and user interface design. I didn't expect us to jump into that as quickly as we did, but there was a lot of interest in the group in 41 00:07:29.020 --> 00:07:45.540 Sharon Markus: discussing how the reporting app would use, the new permissions infrastructure and Eureka, and developing that to work best, for reports. So I'll talk about that a little bit more 42 00:07:45.810 --> 00:07:51.019 Sharon Markus: As we get to that slide. 43 00:07:51.330 --> 00:08:03.689 Sharon Markus: Certainly, we're talking about MetaDB data anonymization and data privacy, so that is a big focus of the discussion, and it's a large… 44 00:08:04.590 --> 00:08:19.100 Sharon Markus: feature request to summarize. There are a lot of different ways that you can anonymize data and different needs for different institutions, and so the group has really been considering, you know, perspectives on that. 45 00:08:19.350 --> 00:08:26.210 Sharon Markus: So we'll… And also, I want to just extend an invitation 46 00:08:26.410 --> 00:08:32.809 Sharon Markus: Anyone who would like to join this group is welcome. We are just work plowing through. 47 00:08:32.909 --> 00:08:51.789 Sharon Markus: data privacy-type issues, and for both reporting app and MetaDB, as they're intertwined. And we're also looking a lot at Folio, because Folio impacts MetaDB. So, it's… we've had a lot of guest speakers, and it's really helped shine the light on… 48 00:08:51.840 --> 00:08:56.330 Sharon Markus: The details that we need to gather to further development in this area. 49 00:08:57.010 --> 00:09:10.169 Sharon Markus: Data anonymization feature development in folio apps, and the impact on MetaDB data. So we've had folks, talk to us about loans and, about requests, and… 50 00:09:10.170 --> 00:09:17.219 Sharon Markus: The most recent being, a discussion about requests. So, the settings that you are… 51 00:09:17.230 --> 00:09:21.560 Sharon Markus: setting. In circulation settings for loans. 52 00:09:21.740 --> 00:09:39.940 Sharon Markus: impact MetaDB in certain ways, and as we understand it, it will be very similar for requests. So, we've been learning a lot about that. Fees and fines are still on the list, but we haven't delved into that much, but because that does, have 53 00:09:40.170 --> 00:09:50.590 Sharon Markus: personally identifiable information in it, we're taking a look at that. It's a little more challenging because a lot of institutions are required to keep 54 00:09:50.840 --> 00:10:00.000 Sharon Markus: data around in the system for finance policy purposes. So, that's a little bit more challenging. 55 00:10:01.810 --> 00:10:17.569 Sharon Markus: We're working on, identifying personally identifiable information in Filio and MetaDB. Generally speaking, because it informs, this work, you know, what data do we need to anonymize, in other words? 56 00:10:17.890 --> 00:10:27.910 Sharon Markus: So we have connections. We actually have several people who are working on the Folio data privacy SIG who are on the MetaDB. 57 00:10:27.940 --> 00:10:38.599 Sharon Markus: A data privacy subgroup, so there's a lot of, collaboration, between those two groups, and, so that's, that's a good thing. 58 00:10:39.230 --> 00:10:47.979 Sharon Markus: For the reporting app, for the Trillium release, we've got, the reporting app user role that's being developed to 59 00:10:48.120 --> 00:10:59.370 Sharon Markus: allow the user to use the build, query, save, query, and run reports tools in the reporting app, but not to have access to modify settings. So this is just a basic reporting app user role. And then, 60 00:10:59.660 --> 00:11:16.279 Sharon Markus: having the reporting app permissions further refined so that they're individual permissions for Query Builder and Run Reports. So, couple of tickets, in Jira, and I believe Mike is already done with them, which is great. 61 00:11:16.940 --> 00:11:23.159 Sharon Markus: We've talked a lot about reports by roles on GitHub, so… 62 00:11:23.310 --> 00:11:29.770 Sharon Markus: The idea is that if you want to, as an institution. 63 00:11:30.380 --> 00:11:33.419 Sharon Markus: Make reports available in the reporting app. 64 00:11:33.950 --> 00:11:37.849 Sharon Markus: that are restricted by functional area. For instance. 65 00:11:38.050 --> 00:11:48.449 Sharon Markus: Only having people in the acquisitions group see Acquisitions report. Only having people in the finance group see finance reports, etc. 66 00:11:48.560 --> 00:11:56.380 Sharon Markus: Then, there needs to be a way to set up the permissions Such that you can… 67 00:11:56.520 --> 00:11:59.540 Sharon Markus: Deliver those reports to those 68 00:11:59.700 --> 00:12:08.829 Sharon Markus: user groups. So, one idea that has been put out there that, Lauren is currently working with index data on. 69 00:12:09.250 --> 00:12:17.030 Sharon Markus: Is the idea that you would be able to have, access to reports. 70 00:12:17.900 --> 00:12:26.889 Sharon Markus: that are in a GitHub directory, specifically in whatever functional area you want to restrict. So, let's say you're 71 00:12:26.990 --> 00:12:28.780 Sharon Markus: finance team. 72 00:12:29.020 --> 00:12:44.189 Sharon Markus: has restricted access to certain reports, then you would have a GitHub repository under reporting app that would say something like fin… this is just an example, something like finance, acquisition, circulation, whatever functional area you want to 73 00:12:44.300 --> 00:12:47.549 Sharon Markus: Separate out, and then… 74 00:12:47.940 --> 00:12:55.810 Sharon Markus: people would be given a role that would allow them to run those particular reports. And we've also talked about the role 75 00:12:55.940 --> 00:13:01.619 Sharon Markus: Being set up so that you could… Have multiple, 76 00:13:01.720 --> 00:13:10.300 Sharon Markus: functional area report access as well. So, if you have a role, for instance, that, would… 77 00:13:10.300 --> 00:13:26.799 Sharon Markus: give you access to finance reports and acquisitions reports, that's totally possible. So, there's a lot of talk about that right now, and we're hearing from Lauren that it looks like we might be able to do something like that. 78 00:13:28.870 --> 00:13:31.949 Sharon Markus: I think? Lauren, can you… 79 00:13:32.430 --> 00:13:48.069 Lauren Seney (Index Data): Yes, we're still really kind of investigating what the best way to do that is, but, and as well as how much work it will take to accomplish that. But I think there is a way to move forward with that. 80 00:13:48.320 --> 00:13:53.519 Sharon Markus: Yay! So, that looks… thank you so much, Lauren. That looks promising. 81 00:13:53.620 --> 00:14:04.739 Sharon Markus: And, so for the MetaDB data privacy next group meeting that we have on Tuesday, March 24th, we're hoping to have a permissions guru. 82 00:14:04.740 --> 00:14:14.559 Sharon Markus: join us to look at these designs and how these reporting rules might work. So we'd like to get a Eureka permissions person in there so that 83 00:14:14.560 --> 00:14:18.609 Sharon Markus: You know, we can design it well and get a little bit more information about that. 84 00:14:19.980 --> 00:14:29.000 Sharon Markus: Also, MetaDB data anonymization and privacy has been a big focus, of course. And… with… 85 00:14:29.120 --> 00:14:31.850 Sharon Markus: Folio, from the Folio app perspective. 86 00:14:31.860 --> 00:14:42.200 Sharon Markus: the… there are data anonymization impacts on MetaDB. So, what loans do when you set that in Folio is that anonymizes the current rows. 87 00:14:42.200 --> 00:14:54.390 Sharon Markus: So, if you have a user ID and a current row, for loans, and the loan has been closed, and you've set it that way in Folio to behave that way, and there aren't any fines and fees associated with it. 88 00:14:54.680 --> 00:14:56.540 Sharon Markus: But… 89 00:14:56.990 --> 00:15:13.340 Sharon Markus: the row will be anonymized, and then over in MetaDB, the current row will get anonymized, but any historical rows that are attached to that, will still have the user ID. So, the historical rows don't get anonymized. 90 00:15:13.510 --> 00:15:19.090 Sharon Markus: As we have seen, Amelia Sutton came and gave us a beautiful, 91 00:15:19.300 --> 00:15:31.159 Sharon Markus: presentation on request app development looks like they're gonna go down the same road. So, in other words, they'll… when you set requests. 92 00:15:31.440 --> 00:15:37.020 Sharon Markus: To the anonymized once they're closed, then the current row 93 00:15:37.250 --> 00:15:41.040 Sharon Markus: Associated with that request that has any kind of… 94 00:15:41.310 --> 00:15:45.160 Sharon Markus: user ID, personally, well, requester ID in this case. 95 00:15:45.410 --> 00:15:51.079 Sharon Markus: Will, the current row will get anonymized, but historical rows will not. 96 00:15:51.580 --> 00:16:00.500 Sharon Markus: So, that's what we're currently looking at from Folio, so it's important to understand that as we move forward. I'm kind of seeing a trend… 97 00:16:00.630 --> 00:16:05.160 Sharon Markus: As I write this and think about it, and that is that… 98 00:16:06.060 --> 00:16:17.160 Sharon Markus: you know, maybe down the road, all we need is a way to anonymize historical data. But, that's just a thought as we go through this. 99 00:16:17.160 --> 00:16:26.589 Sharon Markus: Lauren's got some excellent high-level scenarios that she's working through, for MetaDB data anonymization. 100 00:16:27.080 --> 00:16:35.220 Sharon Markus: And… I'll give you the basics, and then maybe Lauren can jump in for any Any questions or additional? 101 00:16:35.730 --> 00:16:38.010 Sharon Markus: information. 102 00:16:38.670 --> 00:16:43.430 Sharon Markus: So, one, scenario is to keep historical data rows 103 00:16:43.700 --> 00:16:48.009 Sharon Markus: Unanonymized, so in case you want to have history. 104 00:16:48.390 --> 00:16:58.579 Sharon Markus: Another scenario is to keep private data out of MetaDB altogether, so you just have a switch that allows you to say, okay. 105 00:16:59.080 --> 00:17:01.530 Sharon Markus: you know, I want to turn off 106 00:17:01.880 --> 00:17:07.550 Sharon Markus: the synchronization of any personally identifiable information into MetaDB. 107 00:17:07.829 --> 00:17:12.479 Sharon Markus: And this was done for the original, the 108 00:17:12.970 --> 00:17:17.870 Sharon Markus: predecessor of the MetaDB software, the LDP software. 109 00:17:17.990 --> 00:17:25.270 Sharon Markus: So, that is a… that is a direction we could go. The next is to keep data in MetaDB 110 00:17:25.609 --> 00:17:33.210 Sharon Markus: But… the personally identifiable information data, the privacy data in MetaDB, but 111 00:17:33.930 --> 00:17:43.899 Sharon Markus: anonymized in both… in both current and history when triggered in Folio. So that… that is another interesting way to look at it. So to have Folio do the anonymization. 112 00:17:44.210 --> 00:17:48.689 Sharon Markus: Which is an attractive idea from a design standpoint, because 113 00:17:49.200 --> 00:17:54.609 Sharon Markus: The… each app is developing, sort of, its own set of rules around anonymization. 114 00:17:54.960 --> 00:17:58.580 Sharon Markus: Specifically for loan anonymization. 115 00:17:58.910 --> 00:18:10.430 Sharon Markus: you know, the loan has to be closed. The loan, you… and you can… you can set this, on or off, or whatever is preferred by your institution. 116 00:18:10.540 --> 00:18:16.430 Sharon Markus: And, if it's associated with a finer fee, you can set a time frame. 117 00:18:16.640 --> 00:18:25.390 Sharon Markus: of… to keep the data, and, you know, then it's anonymized. So… 118 00:18:26.070 --> 00:18:37.950 Sharon Markus: as Folio works with sets of data coming from different functional areas of the library, it may make a lot of sense to just allow Folio to anonymize 119 00:18:38.130 --> 00:18:44.119 Sharon Markus: The information when that's triggered in Folio. 120 00:18:44.600 --> 00:18:48.919 Sharon Markus: So, those are some examples of what's… 121 00:18:49.570 --> 00:18:52.680 Sharon Markus: Being looked at, and the challenges. 122 00:18:54.330 --> 00:18:55.690 Sharon Markus: One thing that's… 123 00:18:55.820 --> 00:19:06.190 Sharon Markus: kind of a clear-cut path right now to look at, in addition to, sort of, reporting app and getting the permissions figured out, is… 124 00:19:06.480 --> 00:19:17.779 Sharon Markus: Are there data points coming into MetaDB that will not be anonymized in folio, but should be anonymized in MetaDB? What are they? What are they? And so, you know, looking at… 125 00:19:18.470 --> 00:19:28.649 Sharon Markus: These are all areas where we've identified personally identifiable information in folio that comes into MetaDB. 126 00:19:28.970 --> 00:19:35.459 Sharon Markus: And so… The goal is to document this. 127 00:19:35.650 --> 00:19:38.590 Sharon Markus: To study how it works, and then… 128 00:19:38.690 --> 00:19:43.690 Sharon Markus: to, incorporate that into the development. So… 129 00:19:44.550 --> 00:19:48.660 Sharon Markus: I guess… oh, let me… sorry, let me back up. 130 00:19:48.780 --> 00:19:52.219 Sharon Markus: Lauren, is there anything else about 131 00:19:52.330 --> 00:19:55.419 Sharon Markus: This work that you want to mention? 132 00:19:57.130 --> 00:20:02.349 Lauren Seney (Index Data): I think the biggest point I have to make is the slide that you had just moved on to that. 133 00:20:02.350 --> 00:20:02.810 Sharon Markus: Oh. 134 00:20:02.810 --> 00:20:12.990 Lauren Seney (Index Data): I have scenarios, but the challenge now is identifying the data, and what data points should be anonymized. 135 00:20:12.990 --> 00:20:23.340 Lauren Seney (Index Data): I mean, some of these, I don't know if they will ever be anonymized in folio, so there may need to be a mechanism within MetaDP to address them. 136 00:20:23.340 --> 00:20:42.379 Lauren Seney (Index Data): And MetaDB also works with, like, Reshare, so there may be other data points that are required for different platforms when it comes to what data is being put into the system. So, I think this list will be really helpful for us identifying what the data points are. 137 00:20:42.380 --> 00:20:48.959 Lauren Seney (Index Data): What tables we need to be looking at, and then kind of thinking through the scenarios with the different sets of data. 138 00:20:50.470 --> 00:20:51.749 Sharon Markus: Thank you so much. 139 00:20:52.190 --> 00:20:58.930 Sharon Markus: Well, we have your attention. Are there any other areas where there is personally identifiable information? 140 00:20:59.590 --> 00:21:05.750 Sharon Markus: that… Any of you know of that we should be taking into consideration here? 141 00:21:06.150 --> 00:21:07.959 Sharon Markus: Darcy. Yes. 142 00:21:08.260 --> 00:21:18.559 darsi rueda: Yeah, hi, this is Darcy, I'm from Stanford. So, last year… yes, it's 2026. Last year, we started a project on data anonymization. 143 00:21:18.740 --> 00:21:27.860 darsi rueda: identifying fields that would need to be anonymized before, giving the data to EBSCO for, 144 00:21:28.710 --> 00:21:31.990 darsi rueda: Putting into their test automations for new versions. 145 00:21:32.080 --> 00:21:48.750 darsi rueda: And so there is, on the wiki, this data anonymization project, and a spreadsheet or table, something like that, that lists all the folio tables and the ones we think needed to be anonymized. So, some of it is financial data, 146 00:21:48.950 --> 00:21:53.619 darsi rueda: But a lot of it is user data, so, I was thinking comparing 147 00:21:53.770 --> 00:22:02.100 darsi rueda: the list you have here with that list might show a few other places or specific tables that, are affected and have PII. 148 00:22:02.370 --> 00:22:03.729 darsi rueda: So that might be helpful. 149 00:22:04.080 --> 00:22:11.130 Sharon Markus: That… that sounds very helpful, thank you so much. And, you know, we did have… is it Bren… France… 150 00:22:11.740 --> 00:22:14.400 Sharon Markus: French, what is her name? 151 00:22:14.400 --> 00:22:16.049 darsi rueda: Well, Shelly, Shelly Doljak was. 152 00:22:16.050 --> 00:22:17.230 Sharon Markus: Oh, Shelly, yeah. 153 00:22:17.230 --> 00:22:17.580 darsi rueda: Yeah. 154 00:22:17.580 --> 00:22:32.760 Sharon Markus: I think we did have Shelly come talk to us early on, and, we may have… we may have actually had some links to that, so thank you for the reminder. So we'll… we'll connect those, pieces and, 155 00:22:32.940 --> 00:22:37.520 Sharon Markus: reach out to Shelly if… if there's… if there's anything more to add to that. 156 00:22:37.520 --> 00:22:38.210 darsi rueda: That's good. 157 00:22:38.210 --> 00:22:39.970 Sharon Markus: So, thank you so much! 158 00:22:40.630 --> 00:22:52.240 Sharon Markus: Yeah, it's very good to pair that, and I think… and I'm going to bring that to the… I'm in the Folio Data Privacy Sig, and a couple other folks here are as well, so, that would be a good thing for us to… 159 00:22:52.790 --> 00:23:04.820 Sharon Markus: linked to from the data privacy SIG as well, because we're… we've kind of just gotten started with that SIG, restarted, shall we say, with that SIG, and… 160 00:23:05.020 --> 00:23:17.019 Sharon Markus: that is directly relevant to the work that is planned for that SIG, to identify… personally identifiable information. So if a lot of that work has been done by Stanford, thank you so much. 161 00:23:17.160 --> 00:23:22.660 Sharon Markus: And we'll definitely want to incorporate that into development and planning. 162 00:23:23.370 --> 00:23:24.319 Sharon Markus: Thank you. 163 00:23:25.630 --> 00:23:28.720 Sharon Markus: Any other… Thoughts on that? 164 00:23:29.960 --> 00:23:34.170 Sharon Markus: Lauren, did you… were you looking for anything else from this, or… 165 00:23:34.410 --> 00:23:37.099 Sharon Markus: While we've… while we've got folks thinking about it. 166 00:23:38.390 --> 00:23:45.170 Lauren Seney (Index Data): Mostly to get people to think about it, and let us know if you come up with something that's missing. 167 00:23:45.400 --> 00:23:46.200 Lauren Seney (Index Data): Okay. 168 00:23:47.120 --> 00:23:50.250 Sharon Markus: Perfect. Okay, so I'm gonna… I'll bring the… 169 00:23:50.420 --> 00:23:56.000 Sharon Markus: get some links into that more comprehensive information into these different spheres. Katie! 170 00:23:57.150 --> 00:24:09.560 Katie Rahman: Yes, Lauren, when you brought up reshare, that reminded, you know, we're a member of Mobius, and we have DCB OpenRS, and we do have those tables in our MetaDB, and it has patron information. 171 00:24:10.190 --> 00:24:11.990 Katie Rahman: tape. So, I didn't. 172 00:24:12.720 --> 00:24:17.679 Katie Rahman: just to let you know, I don't know if any other DCB libraries. 173 00:24:24.200 --> 00:24:25.170 Sharon Markus: Thank you. 174 00:24:29.000 --> 00:24:34.660 Lauren Seney (Index Data): say, we have, some in-reach libraries as… as well here, and 175 00:24:34.700 --> 00:24:50.940 Lauren Seney (Index Data): I have only just kind of started looking, trying to understand what data is coming into those tables, because I know that process anonymizes loans when they're closed, coming in through… through inReach, but I wouldn't be surprised to find there's… that there's patron data. 176 00:24:50.970 --> 00:25:02.069 Lauren Seney (Index Data): In there as well. So I think these, ILL-type platforms may also be a good place for us to take a look to see if there's anything that we should have included. 177 00:25:02.520 --> 00:25:09.179 Sharon Markus: Okay, wonderful, thank you. I'm gonna just add these… Things here, and then… 178 00:25:09.550 --> 00:25:15.049 Sharon Markus: They're not gonna go in them. I mean, we'll be… we'll add them to the presentation. 179 00:25:15.260 --> 00:25:20.419 Sharon Markus: But I'm also gonna add them to our main notes. I gotta get out of that. Okay. 180 00:25:20.720 --> 00:25:24.329 Sharon Markus: But folks have been, putting 181 00:25:24.860 --> 00:25:30.689 Sharon Markus: putting, things into… I think we have the purchase… do we have the purchaser? Well, maybe not. 182 00:25:30.830 --> 00:25:34.540 Sharon Markus: So let me just add those things here. 183 00:25:35.200 --> 00:25:37.099 Sharon Markus: A second, so… 184 00:25:40.120 --> 00:25:44.850 Sharon Markus: And purchase orders… Thank you, Joanne. 185 00:25:47.860 --> 00:25:48.770 Sharon Markus: Yeah. 186 00:25:53.240 --> 00:25:58.279 Sharon Markus: So, request rush notes on things that were ordered for a faculty member. 187 00:25:58.550 --> 00:25:59.500 Sharon Markus: Yeah. 188 00:25:59.990 --> 00:26:08.899 Sharon Markus: Purchase order tables, and… Oh, thank you, Lauren. Okay, wonderful. 189 00:26:09.700 --> 00:26:11.150 Sharon Markus: Thank you. 190 00:26:12.120 --> 00:26:14.909 Sharon Markus: Alright, so we'll add that as well. 191 00:26:18.640 --> 00:26:27.159 Sharon Markus: And, let's see, there's one more… DCB OpenRS tables, okay. 192 00:26:28.610 --> 00:26:29.960 Sharon Markus: Thank you, Katie. 193 00:26:37.160 --> 00:26:39.530 Sharon Markus: Alright, so we'll clean that up. 194 00:26:40.140 --> 00:26:49.630 Sharon Markus: Okay, any… Questions, comments, suggestions as we do this work in the MetaDB data privacy subgroup. 195 00:26:53.920 --> 00:26:57.579 Sharon Markus: I'm sorry, I'm a little behind on the chat here. Just getting caught up. 196 00:27:14.120 --> 00:27:18.550 Sharon Markus: could we just do… I'm just curious, 197 00:27:19.710 --> 00:27:22.639 Sharon Markus: Could we do a showing of hands? 198 00:27:22.930 --> 00:27:35.060 Sharon Markus: for institutions that have been looking at data privacy issues for MetaDB, and are interested in, in, 199 00:27:35.350 --> 00:27:36.679 Sharon Markus: the development. 200 00:27:38.220 --> 00:27:40.769 Sharon Markus: And I'll put my hand up for that. 201 00:27:42.430 --> 00:27:43.450 Sharon Markus: Yeah… 202 00:27:46.820 --> 00:27:47.690 Sharon Markus: Okay. 203 00:27:48.330 --> 00:27:53.850 Sharon Markus: Yeah, so if your institution, if you can just give us sort of a show of hands, just good to get a sense of… 204 00:27:54.240 --> 00:27:55.150 Sharon Markus: You know? 205 00:27:55.720 --> 00:28:01.200 Sharon Markus: What institutions have been discussing this, or… If it's on your minds. 206 00:28:02.290 --> 00:28:03.200 Sharon Markus: Yeah. 207 00:28:05.340 --> 00:28:06.260 Sharon Markus: Good. 208 00:28:07.370 --> 00:28:24.160 Sharon Markus: And just the other thing, how many institutions… wait, no, lower my hand there. How many institutions have been looking at reporting app and are… are implementing that and thinking about these things like permissions and how it's organized? 209 00:28:31.890 --> 00:28:34.230 Sharon Markus: Yeah… Okay. 210 00:28:36.290 --> 00:28:37.260 Sharon Markus: Alright. 211 00:28:37.880 --> 00:28:40.009 Sharon Markus: Yeah, that's good to get a sense of. 212 00:28:40.260 --> 00:28:42.010 Sharon Markus: Of what people are doing with it. 213 00:28:42.320 --> 00:28:48.170 Sharon Markus: All right. Well, that's, that's, thank you so much, everybody, and, 214 00:28:48.500 --> 00:28:51.259 Sharon Markus: I turn it back to you, Scott. 215 00:28:56.060 --> 00:28:57.610 Scott Perry (UChicago): Thanks, Sharon. 216 00:28:59.160 --> 00:29:05.820 Scott Perry (UChicago): And that's the end of our agenda for today. Do you have any other comments or any other questions for anyone? 217 00:29:13.230 --> 00:29:18.559 Scott Perry (UChicago): Okay, we'll give everyone an extra half hour today. Enjoy. Thank you for coming.