
  • flinders.edu.au
  • Staff
  • Students
  • Library
Flinders University Logo Flinders University Logo
  • Accessing Collections

    Accessing collections

    • Borrowing
    • Branch collections
    • Special collections
    • Document delivery
    • Recommend an item
    • Sendit service
    • Libraries SA Digital
    More
  • Spaces & facilities

    Spaces

    • Book a study room
    • Branch - Central
    • Branch - Gus Fraenkel medical
    • Branch - Sturt
    • Branch - Adelaide theological library
    • Branch - URRSA
    • Disability support
    • Staffed hours

    Facilities

    • Computers
    • Printing & photocopying (Unicard copy shop)
    More
  • Students

    Finding resources

    • Database search
    • Subject related searching
    • Findit@flinders
    • Special collections

    Library skills

    • Library skills
    • Book a librarian
    • Copyright
    • Past exams

    Help & support

    • FLO help
    • Contact us
    More
  • Researchers

    Learning resources

    • Researcher induction
    • Workshops – Research methods

    Services

    • Systematic review help
    • Bibliometrics
    • Research data
    • Statistical tools & services
    • Publishing support
    • ResearchNow
    • ORCiD & academic profiles

    Useful information

    • Archives & records management
    • Keeping up to date
    • Grey literature
    • Advanced searching
    • Endnote
    • Open Access
    • Copyright
    • Theses
    More
  • Staff

    Quick links

    • Readings and resources
    • Accreditation, course approval & curriculum design
    • Information literacy gateway
    • Document delivery
    • Recommend a book
    • Copyright
    • Open Access
    More
  • About

    Quick links

    • Staffed hours
    • Contact us
    • COVID-19 information
    • Bequests
    • Donations
    • Policies & guidelines
    More
  • Databases
  • flinders.edu.au
  • Staff
  • Students
  • Library
  • You have no saved courses.

    Continue to explore your course options.

     
    Explore our courses

    Your saved courses

    {{{courseName}}}
    mail_outline
    delete
    View all saved courses
  • Quick links 
    • FindIt@Flinders
    • Databases
    • Journals
    • My library card
    • Opening hours
    • FAQs (AskFlinders)
    • Student Compass
    • Flinders Learning Online (FLO)
    • Book a study space
    • Flinders dashboard (OKTA)
    • Shop Flinders merchandise

 

Knowledge Management

Researcher resources Knowledge Management

Researcher Resources

     Overview  Statistical tools and services  Data management  Publishing  Publication plan  Researcher identifiers  Knowledge management  eResearch tools and services  Thesis submission  Flinders Academic Commons  Bibliometrics  Keeping up to date  Grey literature  Systematic reviews  Systematic literature searching  Open Access  Online researcher induction

Why Knowledge Management?

Most collaborative projects require some level of knowledge management. Depending on the size and complexity of the project, this can be a simple matter of storing email correspondence in a specific mail folder, or a complex system of nested directory folders shared with project team members on an institutional drive or a cloud storage system.

A logical and transparent knowledge management system is important for the following reasons:

  1. To keep track of work done by team members
  2. To allow team members access to the documents and information they require
  3. To ensure that all team members have access to the latest version of the research and that any changes are made to the correct version (usually the latest version)
  4. To provide historical information on the project and its progress 
  5. To enable new team members to access the project history and take over tasks from others
  6. To keep records and data so that they remain available when the project is finished
     
File Sharing

Shared drives and collaboration spaces

Even in a simple collaboration between two colleagues, it can be useful to maintain a shared file storage space rather than rely on each collaborator to maintain careful version control. Within the institution this can be achieved by setting up shared drives on University servers.

In the case of larger projects, it may be necessary to have different sections of the work shared between different team members, rather than having one common shared space. This can be achieved with file-sharing systems such as Dropbox and One Drive. 

File naming conventions

Even in the context of individual projects, it is good practice when saving a files and creating folder structures to consider what makes that file or folder unique in its intended environment. 

For example, when naming a file for a publication to be submitted to a journal, do not use the name of the journal as the file name. This may be unique in your filing system but will not be unique in the recipient’s system. You could use your own name, but that would not be unique in your own filing system. If the recipient does not provide any guidance, one solution would be to use your name plus the journal’s name, or the title of your article. 

If dates are used as identifying features in file names, especially for sorting, they should be entered in the order YYYYMMDD

If files are to be shared, a file naming standard should be established at the beginning of the project. Stanford University Library provides guidance on best practice for file naming in data management. These guidelines can apply to any kind of shared file environment.

Version control

Careful version control is essential when it is important to keep a record of updates made to a document. For example, a journal editor might wish to keep the author’s original version as submitted, plus an author’s revision after peer review, the copyedited and/or formatted versions sent to the author for their final check, and the final version ready for publication.

Stanford University Library offers simple suggestions for naming different versions of files.

It is preferable to plan logical file names at the start of a project. However, if your file names do not reflect the version of each document clearly, it is still possible to sort a list of files by date and time updated, which can be helpful in establishing this information after the fact. In Windows, view your file list by Details and click on Date Modified to sort chronologically.

Another way that versions can be stored is by using nested folders. For example, in the journal situation above, all contributions for a particular issue might be saved to a folder for that issue, with the formatted versions saved into a folder within that folder (e.g. titled ‘Formatted’) and the versions ready for publication in a folder named ‘Ready’ within the Formatted folder. This system can be useful if there is an output (such as a journal issue, or research outcome) which will draw only on the final versions, as the contents of the folder can be consulted, copied or uploaded in one batch.

Project coordination

The simplest way to coordinate a project is to maintain a spreadsheet or database containing the metadata for various activities. 

For example, a spreadsheet can be used to track the progress of an article through the journal publication process. 

Columns might include title or identification number, author or creator, relevant dates (creation, submission, completion etc), status (in progress, name of person responsible), plus free text columns for notes.

This spreadsheet could be used to create metadata for a research data archive or other output. If so, it is important to use an appropriate metadata standard when setting up the spreadsheet.

If interested parties (e.g. authors, subscribers) need to be notified when an issue is published, a column containing email addresses (with no extraneous characters) can be simply copied into a To: field in an email message (for large lists prefer the BCC field).

Archiving

It is often mandatory under research grant conditions to keep data collected as part of research projects. It is also important to keep records of scholarly activity, such as the conduct of peer reviewing, research methodology, third party agreements etc.

The Flinders Academic Commons is available for retention of research data and author’s copies of publications.

The University records management system has a mandate to collect official documents created by the university. See Archives and Records Management for more information.

Flinders University Logo

Sturt Rd, Bedford Park
South Australia 5042

Ph: 1300 354 633 (Select 3)
Email: library@flinders.edu.au

  • Staff Portal
  • Current students
  • Flinders website

Follow Flinders Library

Facebook - Flinders University Twitter - Flinders University

Website feedback and requests

Disclaimer

Accessibility

Privacy

CRICOS Provider: 00114A     TEQSA Provider ID: PRV12097      TEQSA category: Australian University

Last Updated: 09 Jul 2021
Fearless Logo

This website uses cookies

Flinders University uses cookies to ensure website functionality, personalisation, and for a variety of purposes described in the website privacy statement. For details about these cookies and how to set your cookie preferences, refer to our website privacy statement.

You consent to the use of our cookies if you proceed.

Accept and continue