Uploading Ancillary files for HiGEM

To be able to upload and download ancillary files for HiGEM you will need to have a valid BADC account and have access to HiGEM data.  

Upload the ancillary file to the BADC

This can be done in one of two ways.

1. ftp: ftp to ftp.badc.rl.ac.uk, cd to /incoming/higem/ancil and put the file
2. The BADC file uploader. The file uploader is a www based tool that will allow you to copy files from your local disk to the BADC using a simple web page. There are limits on file sizes that can be moved using this www based method. If you get a message that says you are trying to upload too much data then you should try the ftp method.

During the upload the ancillary file will go into a temporary holding space at the BADC (in the directory /incoming/higem/ancil). You can upload more than one file into the temporary holding space before going on to ingest the files into the HiGEM ancillary archive.

Ingest the file into the Ancillary Archive

This stage performs some checking on the contents of the file, assigns an ancillary type, such as orography or vegetation to the file, allows you to set a version for the file, and finally moves the file to the HiGEM ancillary file archive.

The ingestion is controlled by the HiGEM ancillary web page There is a link to this page from the BADC file uploader, labelled 'Ingest Ancillary Files'.

1. Find the file to ingest. The HiGEM ancillary web page allows you to browse around the temporary space at the BADC to find the file you want to ingest.
2. Set the file type. The HiGEM ancillary web page will check the contents of the ancillary file and, if it can, use these to determine the ancillary type. If it can not determine the ancillary type, for instance if this is the first time that a file of this type has been uploaded then you will be given a chance to set the type.
3. Set the file version. A file version will be suggested on the form, you may set your own version number. This should be a decimal digit. How the version numbers are managed is up to you. A suggestion is to increment the most significant digit only when major revisions have occurred.
4. Move the file to the BADC archive. This stage is done automatically. The files are moved to a location /badc/higem/data/ancil/vnn.m, where n.m is the version number.

Add any notes on the ancillary files to the Workspace

If you have any notes on the ancillary file you have uploaded you can add these to the workspace. You may add notes in text or word or as links to www pages. Notes should be added to the workspace with names that reflect the file type and version e.g. file_type_version. Other comments about the ancillaries can be added to the workspace, either by modifying the notes, by adding new documents, or through a workspace discussion.