WEBVTT 00:18:00.000 --> 00:00:20.610 So the first thing let me share my screen here. 00:00:21.930 --> 00:00:36.220 Again, just to make it clear what we're covering here, because I don't think I've actually mentioned that today. I'm gonna be walking through all the steps for processing acoustic data for anabat using Kaleidoscope Pro. 00:00:39.270 --> 00:00:42.130 This is what that kaleidoscope window is gonna look like. 00:00:44.570 --> 00:00:46.170 Let's see here. 00:00:46.900 --> 00:00:52.750 Could even make sure that your microphones are muted. I can hear someone's someone coming through there. 00:00:55.660 --> 00:01:18.350 OK, so First things first, we've got a colonoscope window open here. The latest version I believe is 5.4 point 8. So always a good idea to check your version. Typically colonoscope will give you a warning if you have an outdated version, but a good idea to check and make sure that there's not a new version available. They do come out with updates quite frequently. 00:01:19.880 --> 00:01:29.930 So First things first, we're going to use this browse button here on the left side of the screen. This is our inputs directory and over here we have the outputs. 00:01:31.150 --> 00:01:42.300 To start with, your page is going to look like this with the default project form down here in the bottom. So we need to select the input directory which is going to be the location of our acoustic files. 00:01:43.270 --> 00:01:46.650 So I have these organized under a folder called RAW files. 00:01:47.990 --> 00:01:49.840 And I'm going to select site one here. 00:01:52.290 --> 00:01:57.380 So we've selected that now we need to select the type of files. In this case I have wave files. 00:01:58.300 --> 00:02:07.970 And now I'm gonna load the NA bat project form. If you have downloaded or if you're following along in the guidance document there. 00:02:09.130 --> 00:02:09.680 That. 00:02:10.640 --> 00:02:11.110 Uh. 00:02:12.470 --> 00:02:30.170 Guidance document does contain a link to download. There's actually two XML forms or project forms for a bat. We're gonna begin with the form anabat metadata form caleidoscope stationary. And so as we load that all of our. 00:02:30.780 --> 00:02:52.070 Metadata fields are gonna appear here, and so we'll just go ahead and fill in this metadata. You can see if you hover the mouse over a window that's gonna provide some tips for formatting or what the field is asking for. In the case of fields that have restricted entries like detector, if you hover it over, it's gonna provide you with all of the. 00:02:54.070 --> 00:03:11.200 Accepted entries in these cases, it's important that whatever you enter in this field matches one of those accepted entries exactly, or you will get an error when you upload those data to the end of that database. So it's a good idea to check those and make sure that you're entering something that matches exactly. 00:03:12.410 --> 00:03:25.660 So we'll begin here. I'm gonna leave grid cell ID blank because I'm gonna provide lat, long and in that case then of that database will use the latitude and longitude to automatically assign it to the corresponding grid cell. 00:03:26.870 --> 00:03:29.580 So we'll provide site name in this case site one. 00:03:31.880 --> 00:03:33.150 Lat long. 00:03:34.050 --> 00:03:36.260 Just going to make some lat long up here. 00:03:38.590 --> 00:03:40.880 Certainly start time and survey end time. 00:03:42.380 --> 00:03:55.390 In this case, I actually need to check I'm using some example files and so I don't actually know when the survey was conducted and I wanna make sure that I'm providing a the correct start and end times. 00:03:56.870 --> 00:04:01.620 Otherwise, those files are gonna give me errors when I uploaded them and so. 00:04:02.650 --> 00:04:07.170 Let's take a look, look and it looks like the survey was 620-2018. 00:04:08.570 --> 00:04:10.110 So we can enter that here. 00:04:11.040 --> 00:04:23.900 This is one of those fields that has a very particular formatting requirements, so if you hover the mouse you can see it's four letter year hyphens to separate the year, month, and date so. 00:04:24.650 --> 00:04:36.020 4 digit year, 2 digit month, 2 digit date, then a capital T and then hours, minutes and seconds separated by colons. So this was 2018. 00:04:38.970 --> 00:04:40.220 620. 00:04:41.780 --> 00:04:42.240 Sure. 00:04:43.340 --> 00:04:44.600 Reasonable time there. 00:04:45.370 --> 00:04:49.040 And then we'll check and see how far the survey went. 00:04:52.120 --> 00:04:55.130 And it looks like all of these files were recorded. 00:04:56.240 --> 00:04:59.450 #VALUE! 00:05:00.710 --> 00:05:04.040 The next day we can do 2018. 00:05:05.710 --> 00:05:07.870 621. 00:05:09.440 --> 00:05:09.830 6. 00:05:09.920 --> 00:05:11.030 It's. 00:05:12.470 --> 00:05:16.070 Just going to double check that those times are correct. 00:05:20.170 --> 00:05:22.880 628 so four, yeah. 00:05:26.180 --> 00:05:26.670 OK. 00:05:27.660 --> 00:05:30.450 Detector this was recorded on audio moth. 00:05:36.020 --> 00:05:37.300 Numbers in here. 00:05:49.270 --> 00:05:55.460 And Cleartype is a restricted categorical field. So if you hover the mouse there, it tells you the options available. 00:06:05.180 --> 00:06:07.880 Here we have another restricted categorical field. 00:06:14.140 --> 00:06:16.290 The contact it's always a good idea. 00:06:16.360 --> 00:06:17.370 Yeah. 00:06:17.780 --> 00:06:18.810 To provide. 00:06:20.040 --> 00:06:38.090 And e-mail address rather than just a name. That's really helpful for us at any bat if we have any questions about the data, it makes it really easy for us to reach out to whoever collected the data rather than just have contact information for the project lead who may not have those answers about some of the nuances of the data. 00:06:39.310 --> 00:06:40.750 So I'm going to skip these. 00:06:42.220 --> 00:07:12.310 Whether covariates fields, unless you're setting up a weather station on site, it's really not necessary to look up whether data from nearby weather stations we at in a bat can do that in a scripted way. That's much easier, and we can collect all of those data from a unified source. That being said, if you do have some sort of weather station where you're collecting weather covariates at the actual site yourself, that's. 00:07:12.390 --> 00:07:14.150 That's great. Please include that. 00:07:16.070 --> 00:07:29.140 And then maybe you can provide some information in the description of your project that notes that you're collecting those weather covariates and that makes it really helpful for us to be able to to understand where those are coming from. 00:07:31.030 --> 00:07:40.000 So the next field this is a required field software type. Again, that's a restricted field, so take a look at those options in this instance. 00:07:42.170 --> 00:07:49.310 You know close scope, 5.4 point X and then species list. My species list is called Colorado bats. 00:07:50.660 --> 00:08:15.030 If you're not familiar with any bat species lists, we have guidance on what those are, how to create them, and how to use them. Again, at anabatmonitoring.org/resources you can find that those resources, but essentially this is just a list of all species that were considered when we were assigning species IDs to these files. So when we get to this step where we're gonna. 00:08:17.270 --> 00:08:25.120 Select our species list in glidescope. It's essentially just going to list all of the species that are checked here, and we save that within our any of that project on the project portal. 00:08:26.360 --> 00:08:29.670 And you're better have my own name here. 00:08:30.630 --> 00:08:33.160 And so that takes care of all of our metadata for this site. 00:08:34.740 --> 00:08:36.770 Our next step is to select an output. 00:08:37.910 --> 00:09:07.380 Folder and make sure that we have a wave files checked here. Now what we're doing by selecting wave files is generating new files. We're gonna create copies of this folder and these copies are gonna actually contain the embedded metadata and we'll then extract that metadata into the anabat bulk upload template. So this is a critical step. If you don't check a box that corresponds with the file types. In this case we have wave files, so we've selected. 00:09:07.630 --> 00:09:30.350 A wave files. We also could generate zero crossing files from WAV files. If your input files are zero crossing, your only option is to generate zero crossing output files. You can't go from zero crossing to wave. You can go from wave to zero crossing, but I like to maintain the original file format so that we don't lose any information here. 00:09:31.470 --> 00:09:53.300 This output directory it's a really good idea to make sure that this output directory is separate from the input directory, and this is gonna make sense in a later step, but what I mean by that is that you don't want this output directory to be nested within the directory that has your original files. So in this case. 00:09:56.040 --> 00:10:24.690 I have the original files in a folder called RAW files and then I'm gonna put all of these new files in a separate directory called process files, and that's gonna basically mirror the directory here under raw files I have sites one through 3 and under process files. I have the same sites one through three. This will make sense later, but this is really crucial and it'll save you a lot of time. So process files. I'm gonna select site one. 00:10:26.060 --> 00:10:28.030 Make sure that I have wave files selected. 00:10:29.180 --> 00:10:31.870 And then we're going to go to the auto ID tab. 00:10:32.160 --> 00:10:57.390 Make sure we've selected bats of North America. We want this set to plus one conservative. That's just telling Kaleidoscope that we want it to be more conservative with the ID. There's three options here, neutral or liberal. Liberal is going to assign. It's gonna give you more species ID, but they're gonna be less accurate. So we want the most accurate setting possible. 00:10:58.060 --> 00:11:06.130 And then we can use the drop down menu here to select the state where the surveys took place. These were in Colorado. 00:11:07.080 --> 00:11:28.360 You do have the option to manually change this, so in a lot of states you may have a portion of the state where species range overlaps and a portion of that doesn't. In those cases, you'd need separate species lists for those areas of the state, but for this example we're just gonna stick with the default Colorado list here. 00:11:30.220 --> 00:11:34.150 Double check that we have everything selected that we want. 00:11:34.810 --> 00:11:36.640 And then we can process our files. 00:11:44.570 --> 00:11:52.680 Oh, and that you can see ran really quick and didn't actually do anything. And I know why. It's because my files for site one. 00:11:53.700 --> 00:11:55.990 We're not in my site one folder so. 00:11:57.920 --> 00:11:59.180 Throw those in there. 00:12:01.890 --> 00:12:02.660 And try that again. 00:12:04.870 --> 00:12:05.820 There we go. 00:12:07.730 --> 00:12:10.960 And quick and then Kaleidoscope is gonna throw up. 00:12:11.830 --> 00:12:14.300 It's summary table here. 00:12:15.120 --> 00:12:18.710 Uh, that's going to show us a summary of all of the species ID. 00:12:20.870 --> 00:12:21.840 And match ratios. 00:12:22.680 --> 00:12:25.130 And it's also going to give us a spectrogram of. 00:12:26.250 --> 00:12:27.630 Very first ID there. 00:12:28.780 --> 00:12:30.170 So you can see this one. 00:12:35.100 --> 00:12:39.070 It's not showing as much here because the scale I think is a little off. 00:12:49.150 --> 00:12:51.230 Then messing around in here a bit. 00:12:52.600 --> 00:12:56.190 So it's looking a little weird. There we go. 00:12:56.910 --> 00:12:58.250 So you can see there. 00:13:00.950 --> 00:13:06.930 At the top, colonoscope is showing us what it's it's best guess at each pulse. 00:13:11.310 --> 00:13:15.380 I believe that is a pallid bat. Is the idea that we're getting here. 00:13:17.670 --> 00:13:25.120 Uh, if you are experienced enough to assign manual ID. 00:13:26.910 --> 00:13:36.760 This would be the the way to do so. So for example and this one, if I take a look at these and I decide no kaleidoscope is wrong. 00:13:37.810 --> 00:13:38.320 Uh. 00:13:39.340 --> 00:13:43.350 I think this is a big brown. For example, you could add your. 00:13:46.310 --> 00:13:51.370 Manual ID here in the window under the spectrogram. 00:13:51.640 --> 00:13:52.870 Enter that. 00:13:53.670 --> 00:13:54.740 And we can see. 00:13:56.120 --> 00:13:57.890 It's going to get added to this table. 00:13:58.850 --> 00:14:01.270 And move on to the next file. 00:14:03.770 --> 00:14:04.750 And so here. 00:14:05.970 --> 00:14:09.770 It's telling us believes this is a Townsend's figured bat. 00:14:10.880 --> 00:14:14.230 You can look through this and say, OK, yes, I agree. 00:14:15.430 --> 00:14:19.260 Click that it's going to add that to the manual ID column. 00:14:20.240 --> 00:14:27.600 And then when we're done, we just click file and save and that automatically will embed those manual ID and those files. 00:14:29.130 --> 00:14:30.120 And click out of this. 00:14:34.060 --> 00:14:53.720 The next step, at least for myself, I always like to rename my files to make sure that the site name is included and that they're clean file names. This is not a requirement for anabat, but it will often save you a lot of trouble when you upload your data to the database. 00:14:54.950 --> 00:15:04.710 One major reason being our database will not accept multiple metadata records for files that have the same name. 00:15:06.210 --> 00:15:07.990 It happens more than you would think. 00:15:10.070 --> 00:15:19.910 Particularly when you have files where the file name is just a timestamp, and in larger projects where you may have multiple surveys occurring. 00:15:20.780 --> 00:15:21.770 During the same. 00:15:23.870 --> 00:15:53.100 Time period and files get recorded at the same time inevitably, and end up with the same file name. So by adding a site name and a grid site ID to the file names, that gives you a unique identifier and unique file name regardless of whether there were other files recorded at the same time and it just saves a lot of trouble. Now there's a few ways to do this, but for those of you who. 00:15:53.980 --> 00:16:00.890 Are comfortable or somewhat comfortable using our. We have a really simple R script for renaming files. 00:16:02.420 --> 00:16:25.910 Also available from anybatmonitoring.org/resources and we have an upcoming webinar that's gonna cover some additional resources for processing acoustic data that will include this R script. You can see here if you're familiar with R this is the script. It's really simple, it just has two packages that you need to load. 00:16:26.990 --> 00:16:34.270 It is annotated that explains all the functions. There's really just two places that need your input. 00:16:34.200 --> 00:16:41.750 The first one is here. We need to input the file directory for the files that we want to rename. 00:16:42.570 --> 00:16:44.280 And in this case it's site one. 00:16:45.820 --> 00:16:49.170 And then we copy and paste this file directory. 00:16:51.370 --> 00:16:52.200 Into this third function here. 00:16:53.430 --> 00:16:54.820 As our root directory. 00:16:57.420 --> 00:17:11.450 And then run these three functions and you can see we've created two lists. We have file names dot OG which is our original file names and then file names and dot new and our root directory and we can run this. 00:17:12.230 --> 00:17:17.620 List here to take a look. So this where these were our initial file names. 00:17:18.630 --> 00:17:21.940 It's actually quite a messy file name there. 00:17:23.440 --> 00:17:43.230 And then down here to change the file names, we have a handful of functions. You've got a string sub which we can designate the starting and ending number of characters that we wanna change, and then what we wanna change it to or we have a string replace where we can enter a particular string that we want to remove. 00:17:44.870 --> 00:17:47.570 And then what? We wanna remove it with in this case. 00:17:48.310 --> 00:17:52.280 It looks like all of our files have this very same. 00:17:53.470 --> 00:17:59.170 Being at the beginning, so I'm gonna copy that and put it into a string replace here. 00:18:01.040 --> 00:18:03.440 And then I just want to replace it with. 00:18:06.070 --> 00:18:09.660 Our file name. I'm not sure what the Grits ID is in this case. 00:18:10.650 --> 00:18:16.660 Because I these are I'm making up the location. So for this example I'm just gonna. 00:18:18.130 --> 00:18:19.360 At site one. 00:18:20.670 --> 00:18:21.960 And then we can run this function. 00:18:23.180 --> 00:18:26.170 And take a look at the list for new file names. 00:18:28.700 --> 00:18:30.670 And it looks like it did not. 00:18:32.660 --> 00:18:33.810 Replaced. 00:18:36.340 --> 00:18:42.200 That, and I suspect it's because we have some special characters in here that sometimes can create problems. 00:18:43.100 --> 00:18:47.070 So let's just take this a little bit at a time and see if we can. 00:18:48.310 --> 00:18:49.750 Troubleshoot what's going on here. 00:18:52.600 --> 00:18:54.900 Make it quick and if it doesn't work then. 00:18:57.250 --> 00:18:58.940 Or we can move on. 00:18:59.770 --> 00:19:02.020 Yep. So we've removed it first part. 00:19:03.860 --> 00:19:06.810 And now we've got six dashes that we want to remove. 00:19:12.720 --> 00:19:16.070 And this is the way that you have to do it. Sometimes is a little bit. 00:19:16.320 --> 00:19:18.070 Trial and error. 00:19:18.600 --> 00:19:20.710 Yep. And so now we've gotten down to. 00:19:22.920 --> 00:19:28.920 The part that we got hung up on, which is those brackets and R sometimes will give you problems. 00:19:30.860 --> 00:19:32.290 So let's just remove the. 00:19:33.080 --> 00:19:34.310 Text within there. 00:19:36.280 --> 00:19:37.000 Take a look. 00:19:39.270 --> 00:19:41.790 And so now we can see it's down to those brackets. 00:19:43.400 --> 00:19:45.730 And so instead we'll use a string sub. 00:19:47.070 --> 00:19:52.570 We'll start with chapter one through character 2, because that would be those brackets. 00:19:54.960 --> 00:19:56.870 And we'll add our site name there. 00:19:59.040 --> 00:19:59.900 Instead. 00:20:02.140 --> 00:20:03.590 Take a look and see if that works. 00:20:07.960 --> 00:20:12.770 Did, but we have now. I've accidentally added two dashes after the site name. 00:20:13.450 --> 00:20:14.460 So. 00:20:15.420 --> 00:20:28.250 Will use a string sub once more. Again, this is kind of trial and error or sometimes with, especially with particularly messy file names. We'll replace that double under score with a single under score. 00:20:30.030 --> 00:20:31.250 And see if that got us there. 00:20:33.870 --> 00:20:37.090 And it did. Now for the last thing, it looks like. 00:20:37.720 --> 00:20:52.290 We want to remove all these zeros that collide Oscope has tacked on. Believe it does that because it is avoiding that duplicate file name situation that I had mentioned earlier. Since these are copies of the original files. 00:20:55.350 --> 00:20:58.770 Most of these are not going to be anywhere near this difficult. 00:20:59.600 --> 00:21:01.860 That was a really, really messy file name. 00:21:04.190 --> 00:21:10.960 But we're just about there with aside from that last one, but for the sake of time, we'll say this is good enough. 00:21:12.300 --> 00:21:18.020 And then we can move on and then these last three functions are just gonna replace. 00:21:18.710 --> 00:21:23.320 The original names with our new names in that folder, so we can run this. 00:21:25.340 --> 00:21:27.830 All of these truths, meaning that it was successful. 00:21:28.690 --> 00:21:32.140 And then we can look at our process files and site one. 00:21:33.240 --> 00:21:35.190 And here's all of our new file names. 00:21:37.950 --> 00:21:41.420 Now because of the way that I did that with the. 00:21:42.450 --> 00:21:47.890 String sub is tacked on site one to all of the file names in here, not just the wave files. 00:21:49.860 --> 00:21:52.450 So I don't wanna forget about our noise folder. 00:21:54.390 --> 00:22:05.670 Which it has renamed. We got a handful of files in here. I'm gonna leave these for the sake of time, but you would want to change the names of these as well. And so up here, you would just. 00:22:06.210 --> 00:22:12.420 For the directory, we just remember to do the same thing we just did to our noise files. 00:22:13.470 --> 00:22:15.080 And then everything's going to be renamed. 00:22:17.140 --> 00:22:33.720 Again, this is not a required step as long as the time stamp is embedded in your files, which nearly every detector is going to do that. But it does make for good data management and it will save you time when you're uploading files to the end of that database. 00:22:35.160 --> 00:22:40.620 So now that we've processed that site, we can extract our metadata. 00:22:41.870 --> 00:23:01.440 Generally speaking, it's a good idea and we'll save you a lot of time to go ahead and process all of your data before you extract the metadata. So in this case, I've already processed two other sites following the same steps in our raw files. You can see sites two and three. 00:23:02.760 --> 00:23:11.990 I've already gone ahead and processed and renamed the files for sites two and three. You can see a clean these names up, so we've got site name, timestamp. 00:23:12.760 --> 00:23:15.810 Format Same here site name timestamp. 00:23:17.300 --> 00:23:17.750 Umm. 00:23:19.070 --> 00:23:31.210 And now This is why I recommended an highly stressed it's a good idea to separate your processed files and original files into separate directories. Is what we're gonna do now. 00:23:32.390 --> 00:23:36.120 Rather than go through individually site by site and extract metadata. 00:23:37.290 --> 00:23:48.060 And our input directory, we're gonna select the parent directory that contains all of our processed files. In this case, it's just processed files. If we had mixed them in with our original files. 00:23:49.140 --> 00:23:58.360 We wouldn't be able to do this because we wouldn't be able to isolate just the process files, but because we have them in a separate directory, I can select processed files. 00:24:00.070 --> 00:24:02.230 And now we can extract metadata from all of these at once. 00:24:03.440 --> 00:24:06.370 We still need to make sure that we designate that these are wave files. 00:24:07.290 --> 00:24:16.760 Next, we're going to replace this metadata form with the output only form and about stationary metadata output only capro. 00:24:17.670 --> 00:24:24.170 You can see that those fields disappear were no longer embedding metadata. We're just reading it into a CSV. 00:24:25.570 --> 00:24:27.380 We're going to select an output directory. 00:24:28.450 --> 00:24:29.120 So. 00:24:29.860 --> 00:24:31.610 Within processed files. 00:24:32.380 --> 00:24:34.010 I mean to make them folder. 00:24:35.280 --> 00:24:36.070 Metadata. 00:24:38.240 --> 00:24:47.780 We'll store all of that. We're gonna unselect the wave file button because we no longer want to create new files. We're just reading metadata from those processed files. 00:24:48.890 --> 00:24:59.900 And then select the auto ID tab and this can be disabled. We've already assigned auto ID to these files so we don't wanna waste processing power on that again. 00:25:00.850 --> 00:25:02.450 Return to the batch tab. 00:25:03.360 --> 00:25:05.400 Make sure everything here looks correct. 00:25:08.100 --> 00:25:10.090 And now we can process these files. 00:25:13.230 --> 00:25:17.920 And we'll take a look in our metadata folder and you can see we've generated some files. 00:25:18.940 --> 00:25:21.590 We're going to be interested in the metadata CSV. 00:25:25.760 --> 00:25:28.390 So open that up and you can see this is the. 00:25:30.170 --> 00:25:31.170 In a bat. 00:25:31.830 --> 00:25:39.580 Stationary acoustic bulk upload template. It's gonna put all of your metadata into the bulk upload template format. 00:25:42.170 --> 00:25:45.180 This is the Afghan empty bulk upload template. 00:25:47.610 --> 00:25:52.970 And you can see this is exactly the same thing, it just has all of our metadata in it. 00:25:53.830 --> 00:25:57.640 And also see we've got site one, site 2. 00:25:58.770 --> 00:26:05.990 And site 3 metadata all in this file. So everything's been extracted into a single CSV. 00:26:07.820 --> 00:26:10.110 Now let's take a look through. 00:26:12.140 --> 00:26:15.070 To ensure that we have all of the metadata that we need. 00:26:17.160 --> 00:26:23.330 These files you can tell are the noise files that I didn't rename in that site one folder. 00:26:24.120 --> 00:26:30.870 They still have the original file names and then here are the files that we renamed following the NA. 00:26:31.820 --> 00:26:32.970 File naming format. 00:26:35.810 --> 00:26:38.700 All of them have timestamp automatically embedded. 00:26:40.740 --> 00:26:42.670 We've got our software version. 00:26:44.110 --> 00:26:56.670 Got manual ID that I changed from a pallid bat to a big brown bat, and then our species list so everything here looks good. We wanna save this with a really descriptive name. 00:26:57.850 --> 00:27:25.250 If you upload multiple files to an NA dot project that have the same name, the newest version is going to overwrite the older version. So we need to make sure that we have a name or we name this file with something descriptive that's not going to be repeated, but otherwise it could be overwritten in the future. So that's something to be very cautious about. In this case we'll call it. 00:27:26.310 --> 00:27:26.800 Uh. 00:27:29.130 --> 00:27:31.100 Kapro metadata. 00:27:35.860 --> 00:27:38.270 Stationary 2022. 00:27:42.570 --> 00:27:43.350 Save it. 00:27:46.330 --> 00:27:48.120 To that metadata folder. 00:27:49.400 --> 00:27:52.370 Also wanna select CSV UTF 8. 00:27:53.960 --> 00:28:08.270 Most of the time they anybody database will accept just a regular CSV, but it definitely likes the UTF 8 versions better and occasionally it will kick out an error. So just out of caution it's always best to select UTF 8. 00:28:09.690 --> 00:28:10.630 Can save that. 00:28:12.420 --> 00:28:18.100 And now I'm going to go ahead and demonstrate how to upload that to an inning that project. 00:28:20.430 --> 00:28:20.890 So. 00:28:21.940 --> 00:28:26.990 Any that I've already logged in and from the home page I'll select my projects. 00:28:28.230 --> 00:28:32.620 I'm a member of several, so I'm going to select my demo project here. 00:28:34.670 --> 00:28:37.590 You have already uploaded quite a bit of data. 00:28:39.890 --> 00:28:45.600 To this project, but we'll select upload survey data, stationary, acoustic. 00:28:46.870 --> 00:28:48.440 We always want to select full metadata. 00:28:49.900 --> 00:28:53.220 And then we'll navigate to the file we just created. 00:29:00.720 --> 00:29:03.620 So it's telling us we got an error here. 00:29:05.320 --> 00:29:08.070 102 errors. Let's see what else. 00:29:09.590 --> 00:29:14.680 So, Corto, this is a common problem for Townsend's bigger bat. 00:29:15.940 --> 00:29:17.440 In Kay pro. 00:29:18.190 --> 00:29:19.580 In a bats. 00:29:21.690 --> 00:29:30.890 Species code is COTO and we don't accept the six digit code that. 00:29:31.810 --> 00:29:34.820 Capro kicks out, so we'll need to change that. 00:29:36.380 --> 00:29:37.110 And then. 00:29:39.070 --> 00:29:39.090 Looks like. 00:29:40.050 --> 00:29:44.920 Audio moth did not come through all the way and it just says audio so. 00:29:46.450 --> 00:29:48.040 We can pull up our file here. 00:29:48.940 --> 00:29:51.910 Make these corrections and the original file. 00:29:55.340 --> 00:29:58.350 And we'll just please find and replace. 00:30:06.330 --> 00:30:07.600 Placed all of those. 00:30:09.700 --> 00:30:10.750 No. 00:30:13.330 --> 00:30:15.650 And these two columns we want to replace. 00:30:16.690 --> 00:30:18.650 Quarto with koto. 00:30:22.930 --> 00:30:23.900 Save my file. 00:30:26.570 --> 00:30:28.590 And if you're not familiar with. 00:30:30.090 --> 00:30:44.820 These kinds of like the accepted species codes and things like that. I deal with this kind of stuff all the time, so I know exactly what it's looking for, but you can click this drop down menu in the auto ID column and Scroll down and find. 00:30:46.370 --> 00:31:12.680 But the accepted codes. So here you can see Coto is the accepted abbreviation for townsends and the reason that this is a little different is because we do have a handful of subspecies of talent's figured bats. So we had to kind of tweak those species codes. So, for example, here we got the Coto and then we have cotton VI for the Virginia bigger bets. 00:31:16.700 --> 00:31:18.790 So looks like now. 00:31:20.230 --> 00:31:21.790 Navigate to that new file. 00:31:22.740 --> 00:31:24.960 You can see here 0 errors. 00:31:26.310 --> 00:31:34.800 It is telling us we're missing one column and we have zero extra columns, so that column that's missing is manual better. 00:31:36.000 --> 00:31:37.590 I just used. 00:31:38.280 --> 00:31:47.210 Uh, when I selected this form, it will colonoscope will automatically save these project forms in the drop down menu here. 00:31:48.290 --> 00:31:54.570 And that's what I used. So this was an older form manual. Better is a relatively new field. 00:31:55.810 --> 00:32:08.740 And I did not select an updated version of that file, the one that you would download and that is linked to an. That guidance document is updated and it will include that manual better field so. 00:32:09.390 --> 00:32:22.040 That's what it's telling us, but always a good idea to check this summary information down here to ensure you don't have any formatting errors and that all of your columns are included. Since we have no errors now, we can go ahead and submit that file. 00:32:24.080 --> 00:32:28.300 And it'll pop up here in the bulk upload status tab here in just a moment. 00:32:31.710 --> 00:32:32.920 And we want to make sure. 00:32:33.680 --> 00:32:40.000 That once this file processes that it has zero errors if it shows up with errors like this for example. 00:32:41.090 --> 00:32:58.090 Those rows are automatically dropped from the database, so those data are not gonna be stored in your project unless you correct those errors and upload them to the partner portal with those corrections now the. 00:32:58.780 --> 00:33:10.450 Our upcoming webinars, one of them is on uploading data to the partner portal. So I'm gonna walk through these steps in a bit more detail, cover some of the most common errors and how to fix them. 00:33:12.040 --> 00:33:27.890 So that may be useful as well. I highly recommend taking a look at our events calendar and joining us for that webinar. If you have a chance. And while this is processing, I can quickly show that so from anybatmonitoring.org. 00:33:29.820 --> 00:33:30.870 To their home page. 00:33:31.990 --> 00:33:33.460 Select the events calendar. 00:33:35.220 --> 00:33:37.750 You can see this is the webinar we're in currently. 00:33:39.890 --> 00:33:42.920 But we have a webinar next week on Thursday. 00:33:43.770 --> 00:33:49.610 Uh, additional resources for processing. Uploading. So that will cover things like those bar scripts. 00:33:50.770 --> 00:33:51.970 And. 00:33:53.820 --> 00:33:56.060 A bunch of other resources for. 00:33:56.780 --> 00:34:11.030 Munging data, rearranging it, formatting it, and those sorts of things, and then it looks like in October, uploading acoustic data, the partner portal, that's what I just mentioned, we'll cover. 00:34:12.960 --> 00:34:21.370 Some of the things that I've just gone over, but in a lot more detail and then we'll get into some of those common mistakes and how to correct those and the easiest ways to avoid them. 00:34:23.600 --> 00:34:29.610 So looks like we got 100 errors. I suspect it's gonna be the start and end times for that. 00:34:32.070 --> 00:34:40.720 Survey that we just filled out, but let's take a look. So let me just show that one more time. So if you click the hyperlink in the errors column. 00:34:41.900 --> 00:34:55.270 It's going to download an error report that will look exactly like your upload, but with two additional columns tacked on to the end that will tell us what the error is and what. 00:34:55.470 --> 00:34:57.400 A row itself. 00:35:00.460 --> 00:35:05.770 And as I suspected, not within the start and end times. So it's gonna tell us. 00:35:06.150 --> 00:35:09.970 The timestamp of the file and then the start time and the end time. 00:35:10.190 --> 00:35:12.190 And so this one was recorded. 00:35:13.080 --> 00:35:28.470 #VALUE! 00:35:29.210 --> 00:35:54.330 Rather than going back into the full file that has in this case only 300 rows, but oftentimes it with real data that could be 10s of thousands of rows of and trying to find those particular rows that have errors, we can make these corrections directly in the error report because it contains all of the metadata and then upload that to sort of supplement that original file. So what I'm going to do is just change the survey start time. 00:35:58.920 --> 00:36:00.690 #VALUE! 00:36:03.870 --> 00:36:04.860 To 619. 00:36:09.590 --> 00:36:11.600 Can replace all of those. 00:36:12.410 --> 00:36:13.750 We'll save this file. 00:36:16.350 --> 00:36:30.640 And then we can upload that to our project because you can see we had 100 errors. So those that were all dropped by the database, which means out of the 302 rows processed only 202 of them were actually stored in this project. 00:36:34.150 --> 00:36:37.190 So I believe this should be in our downloads, Yep. 00:36:39.340 --> 00:36:41.910 And see no errors check. 00:36:43.670 --> 00:36:47.940 Uh, our survey start time is still showing as 620. 00:36:48.770 --> 00:36:50.140 She's not what we want. 00:36:52.000 --> 00:36:53.610 619 here so. 00:36:54.740 --> 00:36:57.810 Maybe it was not saved properly. Let's try that again. 00:37:10.790 --> 00:37:11.080 Hmm. 00:37:15.850 --> 00:37:18.900 Yeah, I'm selecting their own file. Let's make sure this is saved. 00:37:22.850 --> 00:37:25.370 Just save this file to. 00:37:27.340 --> 00:37:29.230 Uh metadata folder. 00:37:33.820 --> 00:37:34.650 F8. 00:37:36.200 --> 00:37:38.790 Survey start time 619. 00:38:04.420 --> 00:38:09.670 For some reason the file still showing 620 as the date. 00:38:10.570 --> 00:38:13.150 And I am puzzled as to why that would be. 00:38:23.250 --> 00:38:25.830 Definitely 619 here. 00:38:27.640 --> 00:38:28.830 To 621. 00:38:39.080 --> 00:38:44.570 But I have no idea what's going on with that, but it's refresh the page and we'll try again. 00:38:45.580 --> 00:38:47.850 In the meantime, this is where. 00:38:48.670 --> 00:38:49.900 We've basically covered. 00:38:51.050 --> 00:38:54.370 All the steps that we're gonna go through, so if anyone has any questions. 00:38:55.230 --> 00:39:04.100 I'm more than happy to start taking a look at those now or answering any questions you may have. We'll see what happens when this file processes. 00:39:10.770 --> 00:39:14.950 And I can't currently see the chat window, but it doesn't look like. 00:39:17.420 --> 00:39:18.590 We have any. 00:39:19.790 --> 00:39:20.920 Anything in the chat yet? 00:39:25.810 --> 00:39:32.840 I'm more than happy to answer any other questions that anyone may have as well. We've got a pretty small group today, so if you have any. 00:39:34.150 --> 00:39:41.860 In about related questions, feel free to ask them even if they aren't directly related to the webinar today. 00:39:51.170 --> 00:40:19.270 Well, you can see that that uploaded without errors, so I'm not sure why that kept showing 6:20, but the database did read the file properly, so that was a kind of strange little glitch there. But you can see now we have our kapro metadata file with the 100 errors. Then we uploaded the corrected error report and those hundred errors were now accepted. So everything looks good.