PILOT logo, post doc PILOT logo, information PILOT logo, literacy PILOT logo, online PILOT logo, tutorial welcome information contents page search and retrieve contents page acquiring and managing information contents page new technologies contents page
digital footprint contents page
copyright contents page IL pilot license contents page databases contents page publication process contents page
Welcome


Writing a data management plan: best practice

There are also a number of common elements that should be considered when developing a file naming strategy, including:

  • Version number
  • Date of creation
  • Name of creator
  • Description of content
  • Name of research team or department associated with the data
  • Publication date
  • Project number
  • Do not use generic data file names that may conflict when moved from one location to another. Ensure filenames are independent of location and if you work on more than one computer ensure that your files are synchronised.
  • File names should outlast the data file creator who originally named the file.
  • Consider how scalable your data file naming policy needs to be. For example, if you want to include the project number, don't limit your project number to two digits, or you can only have ninety nine projects.
GCU logofont +  |   font -  |   Nextsmall plane | small plane Back |  unit home small plane

Creative Commons Licence
PILOT - Writing a data management plan by Edina, University of Edinburgh modified by Marion Kelt, GCU is licensed under a Creative Commons Attribution 4.0 International License. Based on a work at http://datalib.edina.ac.uk/mantra/introduction.html