WEBVTT 1 00:00:04.540 --> 00:00:11.900 A:middle L:90% Yeah. Okay. So yes, I'm Shane Coleman 2 00:00:11.900 --> 00:00:14.109 A:middle L:90% and I'm the data curator here at the library. 3 00:00:14.119 --> 00:00:18.760 A:middle L:90% Uh my job is to help support researchers through identifying 4 00:00:18.760 --> 00:00:23.940 A:middle L:90% the tools that are necessary for storage, archiving uh, and 5 00:00:23.949 --> 00:00:26.399 A:middle L:90% publication. And there's a lot of uh, I 6 00:00:26.410 --> 00:00:29.429 A:middle L:90% don't have all the answers. My job is focused 7 00:00:29.429 --> 00:00:33.780 A:middle L:90% around, you know, supporting any efforts that you 8 00:00:33.780 --> 00:00:35.659 A:middle L:90% might have. Like if you have specific questions and 9 00:00:35.659 --> 00:00:40.210 A:middle L:90% don't have the time to devote uh your effort towards 10 00:00:40.219 --> 00:00:45.740 A:middle L:90% finding the proper storage for your research, you can 11 00:00:45.740 --> 00:00:48.460 A:middle L:90% come to me and we can talk about that. 12 00:00:49.439 --> 00:00:52.039 A:middle L:90% So, a lot of things I'm gonna talk about 13 00:00:52.049 --> 00:00:55.380 A:middle L:90% really already been touched on. Uh what I'm going 14 00:00:55.380 --> 00:00:58.820 A:middle L:90% to try and do in this presentation is identify tools 15 00:00:58.820 --> 00:01:03.969 A:middle L:90% that I've commonly seen use and um really map out 16 00:01:03.979 --> 00:01:06.180 A:middle L:90% , you know, where you can use these tools 17 00:01:06.180 --> 00:01:08.409 A:middle L:90% in the research lifecycle. Um try and pull it 18 00:01:08.409 --> 00:01:11.709 A:middle L:90% all together and talk a little bit about collaborative platforms 19 00:01:11.709 --> 00:01:15.189 A:middle L:90% to integrate with your storage, you're publishing and archiving 20 00:01:15.189 --> 00:01:19.950 A:middle L:90% systems. Uh At first point I really want to 21 00:01:19.959 --> 00:01:26.480 A:middle L:90% make is uh be organized. You know, efforts 22 00:01:26.480 --> 00:01:29.540 A:middle L:90% are put towards writing these data management plans for a 23 00:01:29.540 --> 00:01:34.769 A:middle L:90% reason. Um Sometimes that plan change changes but as 24 00:01:34.769 --> 00:01:38.840 A:middle L:90% long as you maintain an organized system for managing your 25 00:01:38.849 --> 00:01:42.489 A:middle L:90% project, those changes are easier uh to make as 26 00:01:42.489 --> 00:01:45.859 A:middle L:90% you go along. Uh So first thing we're gonna 27 00:01:45.859 --> 00:01:49.010 A:middle L:90% talk about is storage and collecting data and the questions 28 00:01:49.010 --> 00:01:52.230 A:middle L:90% you need to ask yourself before you start collecting data 29 00:01:52.230 --> 00:01:53.879 A:middle L:90% and first and foremost, how much data are you 30 00:01:53.879 --> 00:02:00.810 A:middle L:90% collecting? Um Your local computer or flash drive can 31 00:02:00.810 --> 00:02:06.219 A:middle L:90% be appropriate to store data on to note on that 32 00:02:06.230 --> 00:02:08.180 A:middle L:90% . Make sure you have some backup protocol, you 33 00:02:08.180 --> 00:02:10.530 A:middle L:90% know? Um If you have, if you're working 34 00:02:10.530 --> 00:02:13.599 A:middle L:90% with private data, you know? Yes, you 35 00:02:13.599 --> 00:02:15.250 A:middle L:90% need some sort of security system to maintain that data 36 00:02:15.250 --> 00:02:17.139 A:middle L:90% set on. Um And it may be that you 37 00:02:17.139 --> 00:02:21.169 A:middle L:90% have to use an external flash drive. External hard 38 00:02:21.169 --> 00:02:24.229 A:middle L:90% drive, but just to ensure that that data resides 39 00:02:24.229 --> 00:02:28.270 A:middle L:90% more than just in that one location that way on 40 00:02:28.270 --> 00:02:30.349 A:middle L:90% down the line, you can share that data and 41 00:02:30.349 --> 00:02:35.099 A:middle L:90% move it to a more appropriate system. Uh Again 42 00:02:35.110 --> 00:02:38.349 A:middle L:90% , is your data publicly accessible or confidential? Uh 43 00:02:38.639 --> 00:02:42.229 A:middle L:90% That's gonna be the driving force behind most of your 44 00:02:42.229 --> 00:02:45.039 A:middle L:90% decisions, you know? Uh I forget who has 45 00:02:45.050 --> 00:02:49.150 A:middle L:90% touched on the R. B um policy requirements when 46 00:02:49.159 --> 00:02:52.680 A:middle L:90% you have sensitive data and who has access to that 47 00:02:52.689 --> 00:02:55.300 A:middle L:90% data, um how many collaborate collaborators you have on 48 00:02:55.300 --> 00:03:00.360 A:middle L:90% a project and where those collaborators are located? Um 49 00:03:00.740 --> 00:03:02.979 A:middle L:90% A lot of times, especially as graduate students, 50 00:03:02.979 --> 00:03:10.360 A:middle L:90% you don't have access to uh Pittsburgh University's server system 51 00:03:10.360 --> 00:03:14.289 A:middle L:90% and that maybe the group you're collaborating with, so 52 00:03:14.289 --> 00:03:16.009 A:middle L:90% you have to make sure you have a VPN uh 53 00:03:16.020 --> 00:03:19.740 A:middle L:90% connection that allows you access to that server and and 54 00:03:19.740 --> 00:03:22.199 A:middle L:90% vice versa. If you're hosting a project here, 55 00:03:22.210 --> 00:03:25.469 A:middle L:90% you may have uh collaborators working remotely. So you 56 00:03:25.469 --> 00:03:28.219 A:middle L:90% just have to keep in mind all of these questions 57 00:03:28.219 --> 00:03:30.699 A:middle L:90% . Did you start deciding on what kind of storage 58 00:03:30.699 --> 00:03:32.979 A:middle L:90% media you want for your project? And again, 59 00:03:32.990 --> 00:03:38.469 A:middle L:90% uh make sure you have a method for backing up 60 00:03:38.479 --> 00:03:40.340 A:middle L:90% your data. A lot of cloud systems do have 61 00:03:40.349 --> 00:03:45.639 A:middle L:90% uh you know, backup protocols, but you know 62 00:03:45.650 --> 00:03:50.789 A:middle L:90% , again a lot of cloud systems uh are hackable 63 00:03:50.789 --> 00:03:52.849 A:middle L:90% , so you have to be careful what you choose 64 00:03:53.740 --> 00:03:58.030 A:middle L:90% . Um All right, and on to sharing data 65 00:03:58.039 --> 00:04:01.849 A:middle L:90% , uh again choosing a server system uh within your 66 00:04:01.849 --> 00:04:05.080 A:middle L:90% local department and sometimes I I found that several departments 67 00:04:05.080 --> 00:04:09.780 A:middle L:90% actually charged for using uh server space, so you 68 00:04:09.780 --> 00:04:13.060 A:middle L:90% have to be aware of the actual cost of using 69 00:04:13.069 --> 00:04:18.519 A:middle L:90% these different systems. Um I put arc, arc 70 00:04:18.519 --> 00:04:21.920 A:middle L:90% you on the slide because it's actually a great little 71 00:04:21.920 --> 00:04:27.199 A:middle L:90% software system that allows you to encrypt data. Um 72 00:04:27.209 --> 00:04:32.360 A:middle L:90% So if you're working with some sensitive information i using 73 00:04:32.370 --> 00:04:36.680 A:middle L:90% arc you can actually back up any local drive on 74 00:04:36.680 --> 00:04:41.970 A:middle L:90% your computer, external hard drive, a specific server 75 00:04:41.970 --> 00:04:45.550 A:middle L:90% space. I don't remember the cost of art but 76 00:04:46.040 --> 00:04:48.319 A:middle L:90% no, because of its ability to encrypt the data 77 00:04:48.329 --> 00:04:50.750 A:middle L:90% , you could then move all of your data to 78 00:04:50.759 --> 00:04:56.009 A:middle L:90% google drive and hosted locally. Um It's a very 79 00:04:56.009 --> 00:04:59.779 A:middle L:90% simple tool to use and I highly recommend taking a 80 00:04:59.790 --> 00:05:01.360 A:middle L:90% look at it if you're working uh secure data. 81 00:05:02.639 --> 00:05:11.000 A:middle L:90% Uh huh. Yeah. Yeah. So revisiting the 82 00:05:11.009 --> 00:05:16.459 A:middle L:90% research life cycle. Uh So yeah, the first 83 00:05:16.459 --> 00:05:20.939 A:middle L:90% sections deciding on a topic and your partners and writing 84 00:05:20.939 --> 00:05:23.970 A:middle L:90% your proposal and data management, claiming already kind of 85 00:05:23.980 --> 00:05:25.899 A:middle L:90% touched on two. I want to dive into the 86 00:05:25.899 --> 00:05:30.220 A:middle L:90% actual research process and how that can affect what storage 87 00:05:30.220 --> 00:05:32.959 A:middle L:90% you're using and how you're gonna end up sharing that 88 00:05:32.970 --> 00:05:40.529 A:middle L:90% data. And mm to really get into that, 89 00:05:40.529 --> 00:05:43.209 A:middle L:90% we need to look at the publishing process. So 90 00:05:43.220 --> 00:05:46.279 A:middle L:90% uh typical publishing process, you have a manuscript. 91 00:05:46.290 --> 00:05:50.459 A:middle L:90% Uh You decide to uh published that with some publishing 92 00:05:50.459 --> 00:05:54.449 A:middle L:90% company and they can either reject or accept uh huh 93 00:05:54.839 --> 00:05:56.949 A:middle L:90% your article. And at that point, because of 94 00:05:56.949 --> 00:06:00.230 A:middle L:90% the copy editor edited, uh you may want to 95 00:06:00.240 --> 00:06:04.790 A:middle L:90% talk background a little background Alison. So we asked 96 00:06:04.800 --> 00:06:12.399 A:middle L:90% what was his name? Uh Okay, so dr 97 00:06:12.399 --> 00:06:18.019 A:middle L:90% Delagarza uh what? Engineering? Civil engineering? Uh 98 00:06:18.029 --> 00:06:23.209 A:middle L:90% No, so we had a meeting with him uh 99 00:06:23.220 --> 00:06:28.259 A:middle L:90% to discuss what would be an appropriate model for uh 100 00:06:29.740 --> 00:06:32.850 A:middle L:90% publishing your data along with your article. And we 101 00:06:32.850 --> 00:06:40.379 A:middle L:90% found two points within the publishing lifecycle uh that you 102 00:06:40.379 --> 00:06:44.029 A:middle L:90% could publish a data set. The first being here 103 00:06:44.040 --> 00:06:49.980 A:middle L:90% in this initial submission process and the second um being 104 00:06:49.990 --> 00:06:54.839 A:middle L:90% on down the line once your data has actually been 105 00:06:54.839 --> 00:06:59.990 A:middle L:90% accepted and I don't know if this was really his 106 00:06:59.990 --> 00:07:02.790 A:middle L:90% model that we have been talking about. And what 107 00:07:02.790 --> 00:07:09.350 A:middle L:90% was the journal that he S E. C. 108 00:07:09.740 --> 00:07:16.439 A:middle L:90% Um american. Just to note, publishers are really 109 00:07:16.449 --> 00:07:20.009 A:middle L:90% looking at um this process and where they want to 110 00:07:20.019 --> 00:07:24.209 A:middle L:90% you know they want access to the data, they 111 00:07:24.220 --> 00:07:29.269 A:middle L:90% are reviewing the data that you're collecting throughout your research 112 00:07:29.269 --> 00:07:32.250 A:middle L:90% process. And so I just went ahead and outline 113 00:07:32.639 --> 00:07:36.199 A:middle L:90% um the things you have to take into consideration when 114 00:07:36.199 --> 00:07:43.360 A:middle L:90% you're publishing these points. So first off you must 115 00:07:43.360 --> 00:07:46.629 A:middle L:90% have a citation before your data. Uh At that 116 00:07:46.639 --> 00:07:50.069 A:middle L:90% initial point that way, you know, wherever your 117 00:07:50.079 --> 00:07:53.420 A:middle L:90% data is mentioned in your paper, you have that 118 00:07:53.420 --> 00:07:59.290 A:middle L:90% citation uh data is uh also easier to access. 119 00:07:59.300 --> 00:08:01.850 A:middle L:90% So once you meant your D. O. I 120 00:08:01.860 --> 00:08:05.699 A:middle L:90% . That link can be provided uh wherever your data 121 00:08:05.699 --> 00:08:11.730 A:middle L:90% is being excited. Having that citation means you've already 122 00:08:11.740 --> 00:08:20.360 A:middle L:90% picked archive and you've created that record in some repository 123 00:08:20.839 --> 00:08:24.790 A:middle L:90% . Uh uh So again you know citation must be 124 00:08:24.800 --> 00:08:31.170 A:middle L:90% properly through your manuscript. And at that point once 125 00:08:31.170 --> 00:08:33.850 A:middle L:90% you submit your article and you submit your data to 126 00:08:33.850 --> 00:08:37.899 A:middle L:90% your publisher is going to go through a review if 127 00:08:37.899 --> 00:08:41.509 A:middle L:90% for any reason there's a revision to your data as 128 00:08:41.509 --> 00:08:43.549 A:middle L:90% well as your article just gonna have to be a 129 00:08:43.549 --> 00:08:48.700 A:middle L:90% revision mate. And I mentioned that earlier. Once 130 00:08:48.700 --> 00:08:50.990 A:middle L:90% you meant to do you really want to be confident 131 00:08:50.990 --> 00:08:56.340 A:middle L:90% in the data you have provided revisions in the repository 132 00:08:56.350 --> 00:09:00.509 A:middle L:90% world Can be very tricky. So it's something to 133 00:09:00.509 --> 00:09:05.730 A:middle L:90% stay away from. Uh So personally I really right 134 00:09:05.740 --> 00:09:11.309 A:middle L:90% the idea of a researcher being on top of things 135 00:09:11.309 --> 00:09:15.379 A:middle L:90% and thinking about archival and the duration of their data 136 00:09:15.389 --> 00:09:18.049 A:middle L:90% early on. But sometimes it's not realistic. Which 137 00:09:18.049 --> 00:09:22.899 A:middle L:90% is why I think publishing at that second stage once 138 00:09:22.899 --> 00:09:26.289 A:middle L:90% your article has actually been reviewed really works better for 139 00:09:26.289 --> 00:09:28.990 A:middle L:90% a lot of researchers. Um The big thing about 140 00:09:30.000 --> 00:09:35.470 A:middle L:90% that is you know that one it allows you to 141 00:09:35.480 --> 00:09:39.269 A:middle L:90% review your publisher policy. So if your publisher requires 142 00:09:39.269 --> 00:09:43.870 A:middle L:90% you to use a specific repository or um expects you 143 00:09:43.870 --> 00:09:48.789 A:middle L:90% to publish your data with them, that's the time 144 00:09:48.789 --> 00:09:52.049 A:middle L:90% you can actually compile the data and turn it over 145 00:09:52.059 --> 00:09:56.820 A:middle L:90% to the publisher going back to the citation portion publishing 146 00:09:58.039 --> 00:10:03.889 A:middle L:90% after your manuscript has been accepted. It requires uh 147 00:10:03.899 --> 00:10:07.240 A:middle L:90% in addition to your references so you have to reference 148 00:10:07.240 --> 00:10:11.299 A:middle L:90% your original citation whatever you came up with your manuscript 149 00:10:11.309 --> 00:10:16.259 A:middle L:90% and you have to uh add on your D. 150 00:10:16.259 --> 00:10:18.659 A:middle L:90% O. I. In the reference section. So 151 00:10:18.659 --> 00:10:22.029 A:middle L:90% it's not quite as obvious for someone that's reading through 152 00:10:22.029 --> 00:10:24.919 A:middle L:90% your manuscript. But the D. O. I 153 00:10:24.929 --> 00:10:26.659 A:middle L:90% . Will exist at the end and that link will 154 00:10:26.669 --> 00:10:30.610 A:middle L:90% be there so they can get access to the Yes 155 00:10:30.620 --> 00:10:33.659 A:middle L:90% you would recommend not R. And D. Uh 156 00:10:33.840 --> 00:10:39.990 A:middle L:90% until get the copy editing of a of a uh 157 00:10:41.000 --> 00:10:45.570 A:middle L:90% accepted correct. I would still have your clean data 158 00:10:45.570 --> 00:10:50.159 A:middle L:90% set ready to just deposit a repository. But first 159 00:10:50.159 --> 00:10:54.210 A:middle L:90% things first you may have submitted to numerous numerous publishers 160 00:10:54.210 --> 00:10:58.940 A:middle L:90% right? If one publisher accepts you versus another, 161 00:10:58.950 --> 00:11:01.299 A:middle L:90% their policy may be different on how they want to 162 00:11:01.299 --> 00:11:05.370 A:middle L:90% actually manage that data. So if you wait to 163 00:11:05.379 --> 00:11:09.860 A:middle L:90% archive to that point then you can make that decision 164 00:11:09.340 --> 00:11:11.940 A:middle L:90% . Well he's not, you talked about that. 165 00:11:13.840 --> 00:11:16.740 A:middle L:90% There's your original dataset, raw data and then the 166 00:11:16.750 --> 00:11:22.700 A:middle L:90% data puts into some standardized format for a particular program 167 00:11:22.710 --> 00:11:26.340 A:middle L:90% . That's that that's clearly your original data. You 168 00:11:26.340 --> 00:11:28.519 A:middle L:90% want that you really want that stable when you submit 169 00:11:28.529 --> 00:11:35.029 A:middle L:90% . Although it's always possible that referees steve But the 170 00:11:35.029 --> 00:11:41.309 A:middle L:90% really movable part of this is is if one and 171 00:11:41.320 --> 00:11:43.440 A:middle L:90% this is what I'm really asking about. Are we 172 00:11:43.440 --> 00:11:50.009 A:middle L:90% supposed to also archive the batch files for statistical programs 173 00:11:50.019 --> 00:11:52.620 A:middle L:90% that process the data? Turn that data set into 174 00:11:52.620 --> 00:11:58.250 A:middle L:90% the results of the paper because because those are things 175 00:11:58.250 --> 00:12:01.000 A:middle L:90% that are very likely to change in the, during 176 00:12:01.000 --> 00:12:03.929 A:middle L:90% the referee process. That's a different question. Like 177 00:12:03.940 --> 00:12:11.039 A:middle L:90% we've been talking about software, this is batch files 178 00:12:11.259 --> 00:12:15.690 A:middle L:90% . It's like a text file that you, you 179 00:12:15.690 --> 00:12:20.830 A:middle L:90% know that you execute using state A or so the 180 00:12:20.830 --> 00:12:24.509 A:middle L:90% way I define data, your bash files would actually 181 00:12:24.519 --> 00:12:28.840 A:middle L:90% be data set. Um because you put time and 182 00:12:28.840 --> 00:12:33.779 A:middle L:90% effort to create well they have Yes. Credit does 183 00:12:33.779 --> 00:12:37.799 A:middle L:90% not lead to the tables and figures in the paper 184 00:12:37.799 --> 00:12:41.940 A:middle L:90% with journals, a specific part of the data set 185 00:12:41.950 --> 00:12:48.570 A:middle L:90% replication and that requires very minimum and including like a 186 00:12:48.570 --> 00:12:54.320 A:middle L:90% state of the file or something that does exactly that 187 00:12:54.480 --> 00:12:56.299 A:middle L:90% you really can't do it at the beginning. You 188 00:12:56.309 --> 00:13:03.840 A:middle L:90% have to wait no additional calculation. This this original 189 00:13:03.850 --> 00:13:09.860 A:middle L:90% option is really driven by your basic analytical data. 190 00:13:09.870 --> 00:13:13.200 A:middle L:90% I collected this data. It is what it is 191 00:13:13.210 --> 00:13:20.769 A:middle L:90% , you know, right right in the manuscript until 192 00:13:20.970 --> 00:13:28.649 A:middle L:90% you're actually so a deal I basically it's kind of 193 00:13:28.649 --> 00:13:31.669 A:middle L:90% a freeze put on an object once you have a 194 00:13:31.669 --> 00:13:33.950 A:middle L:90% D. O. I. For it can't change 195 00:13:33.960 --> 00:13:37.860 A:middle L:90% that physical object. Can't that digital object? Sorry 196 00:13:37.860 --> 00:13:43.809 A:middle L:90% not physical can't change. We can however, we 197 00:13:43.809 --> 00:13:46.620 A:middle L:90% are being the sort of data repository community. Can't 198 00:13:46.620 --> 00:13:48.850 A:middle L:90% support versioning. So if something changes, if you 199 00:13:48.850 --> 00:13:52.960 A:middle L:90% need to do additional statistical analysis on the data set 200 00:13:52.960 --> 00:13:54.860 A:middle L:90% , if you need to add files to it, 201 00:13:54.870 --> 00:13:58.309 A:middle L:90% that can certainly occur. But there needs to be 202 00:13:58.309 --> 00:14:01.330 A:middle L:90% a new D. O. I. Generated for 203 00:14:01.330 --> 00:14:05.539 A:middle L:90% that first thing. So the only thing that deal 204 00:14:05.539 --> 00:14:07.220 A:middle L:90% , why does it sort of locks in that one 205 00:14:07.230 --> 00:14:09.350 A:middle L:90% ? Got it. So we can so we can 206 00:14:09.360 --> 00:14:13.549 A:middle L:90% have it. So we could come to like when 207 00:14:13.549 --> 00:14:16.669 A:middle L:90% we're done with our problem we think productive project and 208 00:14:16.669 --> 00:14:18.490 A:middle L:90% we've got to do files, we've got the data 209 00:14:18.500 --> 00:14:24.149 A:middle L:90% files and have it archives. Get a deal and 210 00:14:24.149 --> 00:14:26.240 A:middle L:90% then site that in the manuscripts that we submit. 211 00:14:28.259 --> 00:14:31.460 A:middle L:90% And then when we have to add stuff to it 212 00:14:31.470 --> 00:14:33.889 A:middle L:90% , more data or do files or whatever. Then 213 00:14:33.889 --> 00:14:37.519 A:middle L:90% we come back to you. We we make version 214 00:14:37.529 --> 00:14:43.419 A:middle L:90% two which subsumes and includes everything that wasn't exactly. 215 00:14:43.429 --> 00:14:45.879 A:middle L:90% And then we just modify the D. O. 216 00:14:45.879 --> 00:14:50.990 A:middle L:90% I. Exactly. Everybody's everybody's happy I think at 217 00:14:50.990 --> 00:14:52.529 A:middle L:90% that point. And the way our repository works is 218 00:14:52.529 --> 00:14:56.149 A:middle L:90% that there will be a link in between those two 219 00:14:56.639 --> 00:14:58.210 A:middle L:90% Digital objects to say, Okay, here's sort of 220 00:14:58.210 --> 00:15:01.340 A:middle L:90% version one. Here's the deal for it. Here's 221 00:15:01.340 --> 00:15:03.929 A:middle L:90% version two with these additions. Here's a do I 222 00:15:03.940 --> 00:15:09.360 A:middle L:90% for that but the reasonable manner has everything in the 223 00:15:09.360 --> 00:15:13.409 A:middle L:90% second. It was the first anyway so there's no 224 00:15:13.419 --> 00:15:16.559 A:middle L:90% real need for them to go back. Alright. 225 00:15:16.570 --> 00:15:18.340 A:middle L:90% Sure. Sure. Sure. But it does sort 226 00:15:18.340 --> 00:15:22.110 A:middle L:90% of president, you know the question, I was 227 00:15:22.120 --> 00:15:24.059 A:middle L:90% basically the same thing like so you can have your 228 00:15:24.289 --> 00:15:26.090 A:middle L:90% for your first thing and then you have to edit 229 00:15:26.090 --> 00:15:28.330 A:middle L:90% all your match files. You can have a second 230 00:15:28.600 --> 00:15:33.000 A:middle L:90% before those. Exactly. But the two dl lives 231 00:15:33.000 --> 00:15:35.370 A:middle L:90% will still exist because the D. A. Y 232 00:15:35.370 --> 00:15:37.629 A:middle L:90% . That's the guarantee the whole purpose of the deal 233 00:15:37.629 --> 00:15:41.159 A:middle L:90% is that it exists in the object is sort of 234 00:15:41.169 --> 00:15:45.019 A:middle L:90% frozen. It's a permanent link to it. Even 235 00:15:45.019 --> 00:15:46.450 A:middle L:90% if you don't ever need to go back to the 236 00:15:46.460 --> 00:15:48.580 A:middle L:90% first one, it's still important that their links. 237 00:15:48.580 --> 00:15:50.679 A:middle L:90% So Exactly, people don't mistake it is too. 238 00:15:52.240 --> 00:15:54.620 A:middle L:90% And you know, somebody may be interested in the 239 00:15:54.629 --> 00:15:56.429 A:middle L:90% differences, they may be interested in what you added 240 00:15:56.440 --> 00:15:58.649 A:middle L:90% , they may be interested in comparing the two. 241 00:15:58.659 --> 00:16:03.850 A:middle L:90% So I mean storage and what we're talking about terabytes 242 00:16:03.240 --> 00:16:07.529 A:middle L:90% storage is relatively cheap. So as long as we're 243 00:16:07.529 --> 00:16:11.779 A:middle L:90% not talking about like Two different objects that are each 244 00:16:11.779 --> 00:16:14.629 A:middle L:90% like 50 terabytes. I mean I think it's okay 245 00:16:14.639 --> 00:16:17.860 A:middle L:90% . Both. So okay, I'm gonna jump back 246 00:16:17.860 --> 00:16:21.519 A:middle L:90% out again. Come back to that. There are 247 00:16:21.519 --> 00:16:25.590 A:middle L:90% cases you can when depositing a repository, it can 248 00:16:25.600 --> 00:16:29.509 A:middle L:90% be somewhat complicated when you have a data set, 249 00:16:29.519 --> 00:16:32.429 A:middle L:90% your batch files that you used to process your raw 250 00:16:32.429 --> 00:16:36.269 A:middle L:90% data because sometimes the batch files are the data um 251 00:16:36.279 --> 00:16:40.169 A:middle L:90% you know. Yeah, Creston uh one of our 252 00:16:40.169 --> 00:16:45.600 A:middle L:90% resident uh librarians, he does research based around an 253 00:16:45.610 --> 00:16:48.889 A:middle L:90% algorithm he uses. So he modifies his algorithm for 254 00:16:48.889 --> 00:16:52.509 A:middle L:90% processing data. So he consumes many a huge variety 255 00:16:52.509 --> 00:16:56.250 A:middle L:90% of data. The idea of being he wants to 256 00:16:56.259 --> 00:17:00.110 A:middle L:90% use his algorithm in different scenarios to make sure it 257 00:17:00.110 --> 00:17:03.710 A:middle L:90% processes data and the way he wants it. So 258 00:17:03.720 --> 00:17:08.069 A:middle L:90% when he publishes he's publishing this updated algorithm. Right 259 00:17:08.509 --> 00:17:15.160 A:middle L:90% In your case it sounds like the data is a 260 00:17:15.160 --> 00:17:18.559 A:middle L:90% combination of the algorithm as well as the fire. 261 00:17:18.569 --> 00:17:23.269 A:middle L:90% Apparently what you're calling data subsumes the file, the 262 00:17:23.279 --> 00:17:27.700 A:middle L:90% computer file that have the raw data, the cleaned 263 00:17:27.700 --> 00:17:33.680 A:middle L:90% up file that's readable by a program like data and 264 00:17:33.690 --> 00:17:38.609 A:middle L:90% the do file that creates that that data file and 265 00:17:38.619 --> 00:17:44.259 A:middle L:90% um processing and that's what needs to be our. 266 00:17:44.740 --> 00:17:48.759 A:middle L:90% Yes. And if we have time I'll open up 267 00:17:48.769 --> 00:17:52.230 A:middle L:90% our institutional repository and actually show you a record because 268 00:17:52.240 --> 00:17:55.559 A:middle L:90% when you're requesting A. D. O. Y 269 00:17:55.940 --> 00:17:57.200 A:middle L:90% . Uh huh. That D. O. I 270 00:17:57.210 --> 00:18:00.390 A:middle L:90% . Is for your data set and not specific files 271 00:18:00.400 --> 00:18:03.509 A:middle L:90% . Okay, so a dataset consists of all the 272 00:18:03.509 --> 00:18:07.640 A:middle L:90% metadata related to that project as well as the files 273 00:18:07.650 --> 00:18:10.640 A:middle L:90% that are associated with that project. So I've worked 274 00:18:10.640 --> 00:18:15.059 A:middle L:90% with several um professors here who has 2030, 40 275 00:18:15.069 --> 00:18:21.170 A:middle L:90% Files. They're associated with one project. And technically 276 00:18:22.440 --> 00:18:25.589 A:middle L:90% because all those files are associated with that one project 277 00:18:25.599 --> 00:18:26.859 A:middle L:90% , they all receive the same to you. Why 278 00:18:27.640 --> 00:18:33.549 A:middle L:90% ? There are instances in ways that you can reorganize 279 00:18:33.680 --> 00:18:37.160 A:middle L:90% the engine justify breaking apart that larger project in two 280 00:18:37.170 --> 00:18:44.240 A:middle L:90% phases for project which allows you to meant to do 281 00:18:44.240 --> 00:18:47.569 A:middle L:90% it for the data associated with those different faces. 282 00:18:48.140 --> 00:18:52.490 A:middle L:90% When you're okay, When I write a state of 283 00:18:52.500 --> 00:18:56.960 A:middle L:90% do fine, it reads a file and when it 284 00:18:56.960 --> 00:19:00.190 A:middle L:90% reads the file that has the path right. Clearly 285 00:19:00.190 --> 00:19:03.940 A:middle L:90% that path isn't going to be right. Yeah. 286 00:19:03.440 --> 00:19:07.160 A:middle L:90% And is that? It refers to a particular step 287 00:19:07.170 --> 00:19:08.809 A:middle L:90% , folders and sub folders on on a computer. 288 00:19:08.819 --> 00:19:12.690 A:middle L:90% But I gathered that that's the sort of thing that 289 00:19:12.700 --> 00:19:15.029 A:middle L:90% the end user who reads the archive is supposed to 290 00:19:15.039 --> 00:19:19.490 A:middle L:90% be able figure out customized stuff. Right? Yes 291 00:19:19.500 --> 00:19:25.119 A:middle L:90% . Yes. There are some people working on a 292 00:19:25.119 --> 00:19:30.039 A:middle L:90% way to encapsulate the entire system. Right. So 293 00:19:30.039 --> 00:19:33.079 A:middle L:90% when you got I guess the state do file, 294 00:19:33.079 --> 00:19:37.539 A:middle L:90% it would kind of run through where everything is which 295 00:19:37.539 --> 00:19:41.339 A:middle L:90% libraries state is calling, you know, all that 296 00:19:41.339 --> 00:19:44.079 A:middle L:90% sort of stuff where that lives and package it up 297 00:19:44.079 --> 00:19:47.220 A:middle L:90% , kind of like a virtual machine image. Um 298 00:19:47.589 --> 00:19:48.529 A:middle L:90% And I think the guy who's working on it is 299 00:19:48.529 --> 00:19:53.250 A:middle L:90% that Notre dave I don't have to look that up 300 00:19:53.250 --> 00:19:56.869 A:middle L:90% , but there are people working on that one parent 301 00:19:56.880 --> 00:20:00.089 A:middle L:90% and umbrella, They're weird names. One of them 302 00:20:00.089 --> 00:20:02.529 A:middle L:90% , I think, I'm pretty sure it's umbrella and 303 00:20:02.529 --> 00:20:03.950 A:middle L:90% you search umbrella on your day might come on. 304 00:20:04.190 --> 00:20:07.980 A:middle L:90% I think you know what's called parent. But I 305 00:20:07.980 --> 00:20:10.839 A:middle L:90% mean if somebody is going to be running my file 306 00:20:10.839 --> 00:20:12.390 A:middle L:90% , that better be savvy enough to change a friendly 307 00:20:12.990 --> 00:20:18.670 A:middle L:90% match a file path. That's something as a dating 308 00:20:18.680 --> 00:20:22.819 A:middle L:90% period. When if you create a deposit a record 309 00:20:22.829 --> 00:20:26.099 A:middle L:90% with us in our repository, I would look through 310 00:20:26.099 --> 00:20:27.960 A:middle L:90% that and try and recreate your work on my own 311 00:20:27.970 --> 00:20:30.900 A:middle L:90% . If I had any questions at all, if 312 00:20:30.900 --> 00:20:32.619 A:middle L:90% there was an issue with that, I might send 313 00:20:32.619 --> 00:20:33.339 A:middle L:90% you an email, hey, could you may be 314 00:20:33.339 --> 00:20:37.210 A:middle L:90% right right up to read me file to explain your 315 00:20:37.210 --> 00:20:41.099 A:middle L:90% workflow for using, you know, this this say 316 00:20:41.099 --> 00:20:44.430 A:middle L:90% what line number needs to be changed, correct? 317 00:20:44.440 --> 00:20:47.230 A:middle L:90% I understand. So and that goes in the middle 318 00:20:48.640 --> 00:20:49.500 A:middle L:90% . Yes, Yes. And and that's something I'm 319 00:20:49.500 --> 00:20:52.910 A:middle L:90% actually going to get to. Very short. Yeah 320 00:20:52.920 --> 00:20:56.619 A:middle L:90% . So publishing and archiving. So I I look 321 00:20:56.619 --> 00:21:00.369 A:middle L:90% at publishing and archiving, right? That is the 322 00:21:00.369 --> 00:21:03.799 A:middle L:90% same thing. But they go together when when you're 323 00:21:03.799 --> 00:21:08.019 A:middle L:90% picking an archive for your research, you know, 324 00:21:08.029 --> 00:21:12.759 A:middle L:90% again you're looking at what is my publisher requiring? 325 00:21:14.240 --> 00:21:18.059 A:middle L:90% What are my needs? Do I need uh a 326 00:21:18.069 --> 00:21:22.119 A:middle L:90% repository that restricts access. So we have I see 327 00:21:22.119 --> 00:21:27.019 A:middle L:90% PSR Yeah, that they hold a lot of human 328 00:21:27.029 --> 00:21:33.150 A:middle L:90% research. Uh fig share is open data site is 329 00:21:33.150 --> 00:21:36.359 A:middle L:90% opening. Data site is where we get our D 330 00:21:36.359 --> 00:21:37.710 A:middle L:90% . O. S from. Are you three? 331 00:21:37.720 --> 00:21:41.809 A:middle L:90% That is actually a great tool that I suggest you 332 00:21:41.819 --> 00:21:45.640 A:middle L:90% write down because it is a search tool to locate 333 00:21:45.640 --> 00:21:48.519 A:middle L:90% repositories. Right? So you know if you have 334 00:21:48.529 --> 00:21:52.069 A:middle L:90% any question at all in what kind of repository you 335 00:21:52.069 --> 00:21:56.119 A:middle L:90% should be using, take a look, we're happy 336 00:21:56.119 --> 00:21:56.819 A:middle L:90% to help you, but this is a tool I 337 00:21:56.819 --> 00:22:00.269 A:middle L:90% refer to on a regular basis. So Yeah. 338 00:22:00.940 --> 00:22:07.130 A:middle L:90% And again I think what was your question earlier about 339 00:22:07.140 --> 00:22:15.599 A:middle L:90% choosing repositories? Yes. Uh huh. As I 340 00:22:15.609 --> 00:22:18.759 A:middle L:90% I'm sorry I don't either. It was something about 341 00:22:21.240 --> 00:22:23.839 A:middle L:90% All right. I asked the question what what was 342 00:22:23.849 --> 00:22:34.099 A:middle L:90% that stopped posture Sheriff about moments. Yes. I 343 00:22:34.099 --> 00:22:42.380 A:middle L:90% guess also the blind the boston. Happy you actually 344 00:22:42.390 --> 00:22:48.019 A:middle L:90% right now it's this one of your presentation. Ask 345 00:22:48.019 --> 00:22:55.759 A:middle L:90% the pizza. Well you may have data that for 346 00:22:55.769 --> 00:22:59.869 A:middle L:90% whatever reason you don't want to publish it. You 347 00:22:59.869 --> 00:23:02.269 A:middle L:90% want to archive it and have it there on record 348 00:23:02.279 --> 00:23:04.529 A:middle L:90% . But maybe it's just a completely open data set 349 00:23:04.539 --> 00:23:08.809 A:middle L:90% that you don't want accreditation for. There are repositories 350 00:23:08.809 --> 00:23:11.769 A:middle L:90% out there that are very well suited for that. 351 00:23:12.140 --> 00:23:17.089 A:middle L:90% Again, most repositories have the ability to some sort 352 00:23:17.089 --> 00:23:21.170 A:middle L:90% of citation to put in any manuscript that you're right 353 00:23:22.339 --> 00:23:26.710 A:middle L:90% . But picking an appropriate repository takes time you have 354 00:23:26.710 --> 00:23:30.329 A:middle L:90% to do the research and ask yourself those questions. 355 00:23:30.329 --> 00:23:32.829 A:middle L:90% You know, you know, how long is this 356 00:23:32.829 --> 00:23:34.359 A:middle L:90% repository gonna be around? How, how long they 357 00:23:34.369 --> 00:23:40.529 A:middle L:90% been maintaining data already? Um what policies and sharing 358 00:23:40.529 --> 00:23:44.430 A:middle L:90% agreements uh do they have? And using tools like 359 00:23:44.440 --> 00:23:48.109 A:middle L:90% our three data are great for finding out those big 360 00:23:48.109 --> 00:23:51.130 A:middle L:90% questions that you'd be asking yourself before you publish data 361 00:23:51.140 --> 00:23:55.160 A:middle L:90% . Um and again, who's your target audience? 362 00:23:55.339 --> 00:23:59.190 A:middle L:90% You know, it may be that to get the 363 00:23:59.190 --> 00:24:03.829 A:middle L:90% most exposure you have to find a repository specifically for 364 00:24:03.839 --> 00:24:07.430 A:middle L:90% engineering, computer science, chemistry, whatever you know 365 00:24:07.440 --> 00:24:10.390 A:middle L:90% , whatever it may be. Um but don't forget 366 00:24:10.400 --> 00:24:15.450 A:middle L:90% as long as the publishing company that go with the 367 00:24:15.460 --> 00:24:21.309 A:middle L:90% publisher, manuscript doesn't state, don't publish in blood 368 00:24:21.309 --> 00:24:25.720 A:middle L:90% repository because you have to publish here, publishing as 369 00:24:25.720 --> 00:24:26.480 A:middle L:90% many of these as you can. Just make sure 370 00:24:26.480 --> 00:24:29.660 A:middle L:90% you use the same dont because that's going to give 371 00:24:29.660 --> 00:24:30.849 A:middle L:90% you the most exposure if that's what you're looking for 372 00:24:32.339 --> 00:24:33.460 A:middle L:90% . Um, you know, that that's perfectly acceptable 373 00:24:34.039 --> 00:24:38.220 A:middle L:90% exist. Yeah. A lot of these are absolutely 374 00:24:38.220 --> 00:24:42.130 A:middle L:90% free. Uh, fix shares free. It was 375 00:24:42.130 --> 00:24:48.579 A:middle L:90% when you mentioned described. Yeah PSR is prescribed but 376 00:24:48.579 --> 00:24:52.119 A:middle L:90% there's another one. Okay. Data verse diverse. 377 00:24:52.130 --> 00:24:59.869 A:middle L:90% Its data verse verse path, But the Virginia Tech 378 00:24:59.869 --> 00:25:03.700 A:middle L:90% one, correct. Mm So I should move on 379 00:25:03.710 --> 00:25:07.849 A:middle L:90% another thing to consider. And as a curator, 380 00:25:07.829 --> 00:25:11.960 A:middle L:90% I love when you can help me out with issues 381 00:25:11.960 --> 00:25:18.079 A:middle L:90% like this, try and publish and more open formats 382 00:25:18.079 --> 00:25:19.450 A:middle L:90% . You know, frequently we run across this, 383 00:25:19.460 --> 00:25:23.130 A:middle L:90% you know, data that we no longer have software 384 00:25:23.130 --> 00:25:26.839 A:middle L:90% for or we don't have a license to. That's 385 00:25:26.839 --> 00:25:29.410 A:middle L:90% gonna be the case if you're trying to share your 386 00:25:29.410 --> 00:25:33.269 A:middle L:90% data with people throughout the country throughout the world. 387 00:25:33.279 --> 00:25:34.930 A:middle L:90% Um, so what I have here is just to 388 00:25:34.930 --> 00:25:38.730 A:middle L:90% kind of a wow factor, show you all the 389 00:25:38.730 --> 00:25:44.670 A:middle L:90% different types of with the file types for text files 390 00:25:45.140 --> 00:25:51.490 A:middle L:90% here, raster image files, vector graphics, audio 391 00:25:51.490 --> 00:25:57.000 A:middle L:90% files, video files and database files. So just 392 00:25:57.009 --> 00:26:00.089 A:middle L:90% keep in mind there are a lot of file types 393 00:26:00.089 --> 00:26:00.599 A:middle L:90% out there. There are a lot of open file 394 00:26:00.599 --> 00:26:03.619 A:middle L:90% types out. There were more than happy to work 395 00:26:03.630 --> 00:26:06.900 A:middle L:90% with you. We have a lot of different software 396 00:26:06.900 --> 00:26:11.759 A:middle L:90% here for converting those file times. Um I guess 397 00:26:11.769 --> 00:26:17.059 A:middle L:90% lastly one thing I want to talk about and then 398 00:26:17.440 --> 00:26:21.710 A:middle L:90% collaboration, when we talk about storage, archival and 399 00:26:21.710 --> 00:26:23.170 A:middle L:90% publishing, you know, you really have to talk 400 00:26:23.170 --> 00:26:26.150 A:middle L:90% to, you know, have the conversation, how 401 00:26:26.150 --> 00:26:29.450 A:middle L:90% do these three things relate in a way that is 402 00:26:29.450 --> 00:26:33.859 A:middle L:90% conducive for my working environment. Uh huh. I've 403 00:26:33.859 --> 00:26:37.720 A:middle L:90% tried to put together tools uh and workflows for helping 404 00:26:37.720 --> 00:26:41.940 A:middle L:90% researchers manage the work they do and streamline uh their 405 00:26:41.950 --> 00:26:45.059 A:middle L:90% effort and their research. So what I have here 406 00:26:45.740 --> 00:26:49.890 A:middle L:90% , this is just a rough project file or project 407 00:26:49.890 --> 00:26:52.349 A:middle L:90% folder template that I came up with. I used 408 00:26:52.349 --> 00:26:56.950 A:middle L:90% to work in environmental consulting and they had a great 409 00:26:56.960 --> 00:27:00.309 A:middle L:90% file structure for just organizing projects that I thought was 410 00:27:00.309 --> 00:27:04.460 A:middle L:90% very translatable to research that it goes on here today 411 00:27:04.839 --> 00:27:10.180 A:middle L:90% . Open science framework is an open website that is 412 00:27:10.180 --> 00:27:14.650 A:middle L:90% tremendous for collaborating. Uh You can organize a file 413 00:27:14.650 --> 00:27:17.609 A:middle L:90% structure however you need to you can provide access to 414 00:27:17.609 --> 00:27:22.710 A:middle L:90% specific individuals and you can integrate storage systems like google 415 00:27:22.710 --> 00:27:26.720 A:middle L:90% drive, dropbox. Uh There's a huge variety and 416 00:27:26.720 --> 00:27:30.539 A:middle L:90% they allow um I forget the actual limit but so 417 00:27:30.539 --> 00:27:36.869 A:middle L:90% much on site storage. Uh So you can actually 418 00:27:36.880 --> 00:27:41.009 A:middle L:90% it's similar to um get hub and a lot of 419 00:27:41.009 --> 00:27:45.019 A:middle L:90% these coding sites where you can share notes with people 420 00:27:45.039 --> 00:27:49.170 A:middle L:90% right up wiki documents explaining what work you you've done 421 00:27:49.170 --> 00:27:52.039 A:middle L:90% or what you've been working on. So when your 422 00:27:52.039 --> 00:27:53.640 A:middle L:90% collaborator comes in, you know, they can clearly 423 00:27:53.640 --> 00:27:57.799 A:middle L:90% see a log of what's been going on and what 424 00:27:57.799 --> 00:28:02.349 A:middle L:90% they need to do next. And from a system 425 00:28:02.349 --> 00:28:06.700 A:middle L:90% like this, even from a server space, you 426 00:28:06.700 --> 00:28:10.039 A:middle L:90% can manage these systems. If you really take time 427 00:28:10.039 --> 00:28:15.029 A:middle L:90% to organize uh your project files, you can really 428 00:28:15.029 --> 00:28:17.940 A:middle L:90% find, you know, interface with repository systems, 429 00:28:17.940 --> 00:28:22.509 A:middle L:90% storage, systems, data management plan tools uh collaborate 430 00:28:22.509 --> 00:28:23.829 A:middle L:90% with different universities, you can really integrate with all 431 00:28:23.829 --> 00:28:30.029 A:middle L:90% these uh different parts of your research life cycle as 432 00:28:30.029 --> 00:28:33.910 A:middle L:90% long as you find a system um and organize it 433 00:28:33.910 --> 00:28:36.059 A:middle L:90% in a way that you can actually share the work 434 00:28:36.069 --> 00:28:38.819 A:middle L:90% . So I can't emphasize that enough. Um And 435 00:28:38.819 --> 00:28:41.019 A:middle L:90% again, I'm happy to talk about this and I'm 436 00:28:41.029 --> 00:28:45.069 A:middle L:90% out of time for questions. But if you have 437 00:28:45.069 --> 00:28:47.660 A:middle L:90% anything quick, I don't think any of your mind 438 00:28:47.670 --> 00:28:57.509 A:middle L:90% . Yes. Yeah. Yes. Yeah. So 439 00:28:57.509 --> 00:29:02.769 A:middle L:90% that you can publish on which is homers for government 440 00:29:10.339 --> 00:29:26.839 A:middle L:90% ? Yeah. Yeah. Mhm. Mhm. Yeah 441 00:29:29.839 --> 00:29:37.839 A:middle L:90% . Uh huh. Yes. Mhm. It's just 442 00:29:37.849 --> 00:29:42.230 A:middle L:90% a collaborative environment. So what you do is you 443 00:29:42.230 --> 00:29:47.509 A:middle L:90% come in here and uh you create a project. 444 00:29:47.519 --> 00:29:56.740 A:middle L:90% So I think I'm already on a private Yeah. 445 00:29:56.750 --> 00:30:03.059 A:middle L:90% Creative project and whatever you want, I've created a 446 00:30:03.059 --> 00:30:11.950 A:middle L:90% couple of template projects actually open. Yeah. Okay 447 00:30:14.240 --> 00:30:18.880 A:middle L:90% . Mhm. And you set up whatever type of 448 00:30:18.880 --> 00:30:26.490 A:middle L:90% file structure that you want and get a contributor at 449 00:30:26.490 --> 00:30:30.529 A:middle L:90% new contributors to your project. You can upload single 450 00:30:30.529 --> 00:30:37.190 A:middle L:90% files, you can go to specific folders and write 451 00:30:37.190 --> 00:30:41.430 A:middle L:90% notes for that particular section. So if you uploaded 452 00:30:41.430 --> 00:30:45.029 A:middle L:90% a new file and you needed joe in new Hampshire 453 00:30:45.039 --> 00:30:47.390 A:middle L:90% to review this file, you can write a note 454 00:30:47.390 --> 00:30:48.279 A:middle L:90% in there and there's a time stamp. So joe 455 00:30:48.279 --> 00:30:51.640 A:middle L:90% knows, hey, you dumped this file and he 456 00:30:51.640 --> 00:30:53.039 A:middle L:90% needs to review it and and get back to you 457 00:30:53.049 --> 00:30:56.440 A:middle L:90% on what the next steps are. It's just a 458 00:30:56.440 --> 00:31:00.119 A:middle L:90% great environment for collaborating in those ways. And another 459 00:31:00.119 --> 00:31:06.480 A:middle L:90% thing is uh jenny was the settings that we had 460 00:31:06.490 --> 00:31:10.769 A:middle L:90% the Yes. So here is where you can link 461 00:31:10.769 --> 00:31:15.829 A:middle L:90% up amazon, dropbox diverse fig share um, any 462 00:31:15.829 --> 00:31:18.039 A:middle L:90% of these sites. So you can actually have bulk 463 00:31:18.049 --> 00:31:22.559 A:middle L:90% data and have access to that data through this site 464 00:31:22.569 --> 00:31:29.809 A:middle L:90% . So what happened? So it actually takes you 465 00:31:29.819 --> 00:31:33.559 A:middle L:90% to the specific, you can opens it within. 466 00:31:33.940 --> 00:31:38.059 A:middle L:90% Yes, but you can spit take a subdirectory. 467 00:31:38.640 --> 00:31:41.630 A:middle L:90% Uh, so if you have, I'm sure you 468 00:31:41.630 --> 00:31:44.650 A:middle L:90% do a ton of information that you don't want to 469 00:31:44.660 --> 00:31:47.619 A:middle L:90% be accessible. You just go to that subdirectory and 470 00:31:47.619 --> 00:31:48.799 A:middle L:90% that project on your google drive and that's all they 471 00:31:48.799 --> 00:31:52.990 A:middle L:90% have access to. So you do actually map. 472 00:31:53.039 --> 00:31:57.130 A:middle L:90% So if you want information science project framework projects could 473 00:31:57.140 --> 00:32:00.269 A:middle L:90% be linked to a specific project folder on my Children 474 00:32:02.039 --> 00:32:05.339 A:middle L:90% , but I believe so, I was having issue 475 00:32:05.339 --> 00:32:07.490 A:middle L:90% with that earlier, so but they're still working on 476 00:32:07.490 --> 00:32:10.740 A:middle L:90% when we worked on somebody else's faculty, um they 477 00:32:10.750 --> 00:32:15.200 A:middle L:90% wanted to have edit within this, but you can't 478 00:32:15.210 --> 00:32:17.480 A:middle L:90% edit google doc, you have to view edit view 479 00:32:17.490 --> 00:32:22.500 A:middle L:90% only. So it appears whenever you edit, it 480 00:32:22.500 --> 00:32:23.559 A:middle L:90% was in a good driver that was in this and 481 00:32:23.839 --> 00:32:27.200 A:middle L:90% open Science when people say they are working on it 482 00:32:27.210 --> 00:32:32.759 A:middle L:90% hasn't happened yet. Oh, any other questions? 483 00:32:34.339 --> 00:32:37.299 A:middle L:90% But this is pretty powerful. Yeah, the all 484 00:32:37.299 --> 00:32:39.470 A:middle L:90% the FBI it sounds like what the storage might be 485 00:32:39.480 --> 00:32:45.859 A:middle L:90% really good for is is so everything you can set 486 00:32:45.859 --> 00:32:47.349 A:middle L:90% it up so that everything you've done on your open 487 00:32:47.349 --> 00:32:52.289 A:middle L:90% Science and we'll automatically get backed up to one or 488 00:32:52.299 --> 00:32:54.140 A:middle L:90% more. But you might want to actually do your 489 00:32:54.150 --> 00:33:00.619 A:middle L:90% collaborative work just within the Open Sign Current work framework 490 00:33:00.630 --> 00:33:04.940 A:middle L:90% and you edit it there and then archive to easily 491 00:33:04.950 --> 00:33:07.329 A:middle L:90% one of these other. Right? You get that 492 00:33:07.329 --> 00:33:12.140 A:middle L:90% work I uh, that sort of intended to do 493 00:33:12.140 --> 00:33:14.480 A:middle L:90% . I I haven't explored all of those functions, 494 00:33:14.480 --> 00:33:20.309 A:middle L:90% but I've tried to do the basics. You are 495 00:33:20.309 --> 00:33:32.859 A:middle L:90% you ready? Uh huh. Mm. Okay. 496 00:33:34.440 --> A:middle L:90% Yeah.