Council on archives international records management trust



Download 0.83 Mb.
Page22/44
Date20.10.2016
Size0.83 Mb.
#5745
1   ...   18   19   20   21   22   23   24   25   ...   44

Saving documents


To ensure that electronic information is available, understandable and usable, it is necessary to apply a structure to the way it is stored. Organisations can offer guidance on the co-ordinated management of documents in shared directories and files. It is helpful to explain that the structure of the activity can provide a model for the storage structure: for example, the function of land registration may be identified in the name of the electronic file, so that people can link the record to the function it reflects. Suggestions can also be made about the protection and disposal of electronic documents. Often guidelines also include examples of naming conventions for directories, sub-directories and documents.

When developing the standard system, first consider the operating system and its particular constraints. Most operating systems provide for structured names for directories, sub-directories and files. The guidelines draw on examples consistent with a Microsoft Windows 98 environment. The same principles presented can be adapted and applied to other operating environments.

If information is stored on paper, minimal identifying information should be sufficient. For example, it may be enough to record the computer directory and electronic file name in a line of text that shows up on the printed document: C:/Projects/Land Registration/regions.doc.

For more information on the concepts of computer operations and the components of computers, see Understanding Computers: An Overview for Records and Archives Staff.

Structuring the Directory


The first activity should be to structure the directory, including the directory and sub-directory levels. The directory system can be compared to a tree, with directories and sub-directories branching off from the main, or root directory, resulting in a hierarchical structure.

Directories should be structured to suit the needs of the department. They can be structured in many different ways (such as by user names, dates, organisational units, type of document and so on). However, organisations should base the structure on the department’s functions, programmes and activities to ensure that the documents are organised according to the way the department, and consequently the employee, works (this approach is discussed in depth later in the guidelines). The controlled vocabulary used by a registry can serve as the basis for naming directories and files.

Documents can then be stored as files under the appropriate directories and sub directories. Directory names do not need to be repeated in the file names.

The following principles should be kept in mind when designing the structure for electronic directories.



  • The structure should be simple and logical.

  • The arrangement of the directories should proceed from the general to the specific. In other words from activity to a sub-activity to tasks and sub-tasks. For example, proceed from FINANCIAL MANAGEMENT to ACCOUNTS ADMINISTRATION to PAYMENTS

  • Clear and consistent terminology should be used to when naming directories and files. This will permit the originating users as well as others to quickly identify and retrieve documents.

If an organisation chooses to base its directory structures on its programmes and activities, these should follow a hierarchical arrangement. This can be easily adapted to the directory/sub-directory hierarchy. Existing subject file classification systems for managing paper files are often based on this structure. If this is the case, this will provide a good means of linking the paper and electronic parts of systems.

For information on controlled vocabularies and file classification systems, see Organising and Controlling Current Records.


Naming Conventions


Departments should set up standard conventions for naming the directories and the files stored under the directories. There are many benefits to establishing conventions for directory and file names.

  • Documents can be easily and quickly located in personal or shared workspace, on diskettes, on backup systems or in off-site storage.

  • Since adopting naming conventions allows employees to recognise documents that others may have filed, they can be reused, reducing the risk of duplicating someone else’s work.

  • The file name can be used to distinguish final versions from drafts.

It is best to use standard abbreviations whenever possible.

  • The records manager can help identify standard abbreviations already in use in the department.

  • The government telephone directory often contain abbreviations for names of departments and agencies.

  • The post office often provides abbreviations for regions.

  • Department-wide conventions for names of individuals, locations and so on can be developed and disseminated.

A problem arises when users exchange documents on diskettes or by electronic mail. Documents with the same names cannot be stored in the same directory. Therefore, users need to save documents with the same name in separate directories.

Document version controls


The degree to which a particular document can be revised before being filed as a record should be a matter for corporate procedures and user guidance. After a document reaches its final version as a record, editing should be prevented as far as possible.

New and related versions of the record can be created by making and editing a copy, and saving this as a new record. For example, it may be appropriate to retain various version of a document as it passes through draft to finalisation.

The record-keeping system should be capable of linking together versions of the same record, either automatically by the system or through the use of strict naming conventions, to ensure that the latest version is retrieved by a user search. The user should be aware that earlier versions of the record exist in the system.



Download 0.83 Mb.

Share with your friends:
1   ...   18   19   20   21   22   23   24   25   ...   44




The database is protected by copyright ©ininet.org 2024
send message

    Main page