The Metadata file can be prepared in excel or google sheets and must be saved as a comma-separated values file (.csv).
The “Format” and “On import checks” described in Table 1 indicate the format and requirement of fields for the YYYY-MM_Project.name_Method_Metadata.csv file to be successfully uploaded.
An example template is provided here, the head of which is shown in Table 2. Additional columns with project specific information can be added to the end of the sheet as required.
Two example R workflows are provided, to create multiple $Metadata.csv files from either:
And examples of how to fix common formatting issues for YYYY-MM_Project.name_Method_Metadata.csv files are given:
Table 1. Format of the $Metadata.csv file, note the tables described below are transposed (rows for columns) for formatting convenience.
Name | Format | On Import checks |
---|---|---|
Sample | String | Required. Cannot be blank |
Latitude | Decimal degrees | Required. Is numeric between -90 to 90 |
Longitude | Decimal degrees | Required. Is numeric between -180 to 180 |
Date | String in YYYYMMDD format e.g. 19990101 for 1st of January 1999 | Required. Is YYYYMMDD |
Time | hh:mm:ss | Required. Is hh:mm:ss |
Location | String | Column name but can be blank |
Status | MPA status (must be Fished, No-take, I, II, III, IV, V, VI) | Column name but can be blank |
Site | String | Column name but can be blank |
Depth | Numeric | Required. Is numeric |
Observer | String | Column name but can be blank |
Successful.count | String (must be Yes or No) | Required. Cannot be blank |
Successful.length | String (must be Yes or No) | Required. Cannot be blank |
Others | As many other user defined column names as required | Can be blank |
Table 2. Head of example YYYY-MM_Project.name_Method_Metadata.csv file 2015-01_Montes.transect-stereoBRUVs_Metadata.csv
Sample | Latitude | Longitude | Date | Time | Location | Status | Site | Depth | Observer | Successful.count | Successful.length |
---|---|---|---|---|---|---|---|---|---|---|---|
NCB606 | -20.408 | 115.48192 | 20150117 | 08:45:00 | Montes | Fished | 1 | 25.7 | Tim | Yes | Yes |
NCB607 | -20.407 | 115.47612 | 20150117 | 08:48:00 | Montes | Fished | 1 | 29 | Tim | Yes | Yes |
NCB608 | -20.405 | 115.46842 | 20150117 | 08:56:00 | Montes | Fished | 1 | 30.4 | Tim | Yes | Yes |
Troubleshooting tips
Changing the default program that opens .txt files to Excel may help with this process.
- Beware - Excel will parse any recognisable date and time data into the computer’s system default format - which may not match the required format for the $Metadata.csv.
- You may think you have the date format correct - but if you open the file in Excel - it will change the format!
- You can use R to format your metadata.csv file.
-
Another option is to set Windows system defaults, Click on Start>Control Panel>Region and Language (this will differ between versions of Windows) and ensure the defaults match those below:
- It is recommended that the above template for Metadata is used for new Campaigns to reduce data manipulation and re-formatting before uploading to GlobalArchive.
- If any required data is missing, enter obvious dummy values that can be corrected in the future (e.g. for Depth enter 0, for Latitude or Longitude enter a site position or local port position, Time enter 00:00:00).
- If your longitude and latitude are in the wrong format use a batch converter tool such as: https://www.earthpoint.us/SignIn.aspx. A free account can be requested if it is for educational purposes.
- For an EM/Stereo import, the “Sample” value must match the OpCode in EventMeasure exactly and is case sensitive.
TIP: To make sure these match use the list of OpCodes in the Info file to create your Metadata file (the Info file is exported during the EventMeasure datatable process outlined below). If any of these do not match open the corresponding .EMObs file in EventMeasure, edit the OpCode in the information field and save the file before exporting datatables.
- To fix formatting issues using R, see Fix format issues in $Metadata.csv