RCRG logo   Recordkeeping Metadata




Monash University Logo

Search

About RCRG - Contact Details, Map, Personnel, 
Research Areas: Metadata Control, Continuum Modelling & Research, Recordkeeping & Legal Systems          

Research - SPIRT Recordkeeping Metadata Project, TIF, InterPARES Project          

Publications - Author List, Title List          

Consulting - Recordkeeping Metadata, Recordkeeping Regimes, Personnel, Clients          

Links - Related Research Groups, Useful Resources          

SiteMap          


© 1998 Records Continuum Research Group, Monash University. All Rights Reserved.

 

Recordkeeping Metadata Schema (RKMS) Version 1.0 Register


Prepared by Sue McKemmish, Glenda Acland, Kate Cumming, Barbara Reed and Nigel Ward 31 May 2000 (with revised and updated examples September 2000, January 2001, August 2001)

PDF version (1.73 Mb)


RKMS ENTITIES

RKMS ELEMENTS

SCHEMES




Recordkeeping Metadata Schema (RKMS) Version 1.0 Register


Prepared by Sue McKemmish, Glenda Acland, Kate Cumming, Barbara Reed and Nigel Ward 31 May 2000 (with revised and updated examples September 2000, January 2001, August 2001)

RKMS ENTITIES

  • BUSINESS
    • BUSINESS-RECORDKEEPING
  • AGENTS
  • RECORDS

RKMS ELEMENTS

ENTITY SWITCH: BUSINESS
RKMS01
RKMS02
RKMS03
RKMS04
RKMS05
RKMS06
RKMS07
RKMS08
RKMS09
RKMS10
RKMS11
RKMS.Business.CategoryType
RKMS.Business.Identifier
RKMS.Business.Title
RKMS.Business.Date
RKMS.Business.Mandate
RKMS.Business.Place
RKMS.Business.FunctionalClassification
RKMS.Business.Relation
RKMS.Business.Abstract
RKMS.Business.Language
RKMS.Business.BusinessRules

ENTITY SWITCH: BUSINESS-RECORDKEEPING

RKMS12
RKMS13
RKMS14
RKMS15
RKMS16
RKMS17
RKMS18
RKMS19
RKMS20
RKMS21
RKMS22
RKMS.BusinessRecordkeeping.CategoryType
RKMS.BusinessRecordkeeping.Identifier
RKMS.BusinessRecordkeeping.Title
RKMS.BusinessRecordkeeping.Date
RKMS.BusinessRecordkeeping.Mandate
RKMS.BusinessRecordkeeping.Place
RKMS.BusinessRecordkeeping.FunctionalClassification
RKMS.BusinessRecordkeeping.Relation
RKMS.BusinessRecordkeeping.Abstract
RKMS.BusinessRecordkeeping.Language
RKMS.BusinessRecordkeeping.BusinessRules

ENTITY SWITCH: AGENTS [PEOPLE]

RKMS23
RKMS24
RKMS25
RKMS26
RKMS27
RKMS28
RKMS29
RKMS30
RKMS31
RKMS32
RKMS.Agents.CategoryType
RKMS.Agents.Identifier
RKMS.Agents.Title
RKMS.Agents.Date
RKMS.Agents.Mandate
RKMS.Agents.Place
RKMS.Agents.FunctionalClassification
RKMS.Agents.Relation
RKMS.Agents.Abstract
RKMS.Agents.Language

ENTITY SWITCH: RECORDS

RKMS33
RKMS34
RKMS35
RKMS36
RKMS37
RKMS38
RKMS39
RKMS40
RKMS41
RKMS42
RKMS43
RKMS44
RKMS45
RKMS46
RKMS47
RKMS48
RKMS49
RKMS50
RKMS51
RKMS.Records.CategoryType
RKMS.Records.Identifier
RKMS.Records.Title
RKMS.Records.Date
RKMS.Records.Mandate
RKMS.Records.Place
RKMS.Records.FunctionalClasification
RKMS.Records.Relation
RKMS.Records.Abstract
RKMS.Records.Language
RKMS.Records.SubjectClassification
RKMS.Records.DocumentaryForm
RKMS.Records.Appraisal
RKMS.Records.Control
RKMS.Records.Preservation
RKMS.Records.Retrieval
RKMS.Records.Access
RKMS.Records.Use
RKMS.Records.EventHistory

SCHEMES

RKMS SCHEMES

  • RKMS Category Type Scheme (2000-03-31)
  • RKMS Entity Relationships Scheme (under development)
  • RKMS Extension for ISO 8601 (2000-03-31)
  • RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31) (under further development)

Use of Schemes for Dates

List of other Schemes referred to in this document

Australian Schemes

Global Schemes

RKMS01
Entity Switch BUSINESS
Name CATEGORY TYPE
Identifier RKMS.Business.CategoryType
Definition The name of the type of Business entity.
Description This element identifies the type of business entity being described with reference to the Transactional Axis of the Records Continuum Model. Business entities include classes of business transactions, business activities, business functions and ambient functions (broad societal purposes). The Category Type element is intended to function as a handshake or introduction for the metadata record, e.g.: "Hello, I'm a description of a class of business transaction."
Element Qualifier  
Value Components  
Scheme

Mandatory Scheme
Use to qualify the whole value of the Business.CategoryType element:

RKMS Category Type Scheme (2000-03-31)

Comments  
Examples

Ambient Function
RKMS.Business.CategoryType = Ambient Function [RKMS Category Type Scheme (2000-03-31)]

Business Function
RKMS.Business.CategoryType = Business Function [RKMS Category Type Scheme (2000-03-31)]

Business Activity
RKMS.Business.CategoryType = Business Activity [RKMS Category Type Scheme (2000-03-31)]

Business Transaction
RKMS.Business.CategoryType = Business Transaction [RKMS Category Type Scheme (2000-03-31)]

RKMS02
Entity Switch BUSINESS
Name IDENTIFIER
Identifier RKMS.Business.Identifier
Definition A unique identifier assigned to the Business within a particular domain.
Description The unique identifier may include the name of the business, a date associated with the Business and/or function, activity and transaction descriptors drawn from a functional classification scheme or thesaurus. Its data value may be the same as, or incorporate components of the data value for, the Business.Title, Business.Date or Business.FunctionalClassification element.
Element Qualifier  
Value Components  
Scheme

Relevant Schemes:
May be used to qualify the whole value of the Business.Identifier element:

ABS1220.0 - Australian Standard Classification of Occupations (ASCO) Second Edition (1997)
ABS1292.0 - Australian and New Zealand Standard Industrial Classification (ANZSIC) (1992)
AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)
KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)

Comments One important use of this element is to point or provide a link to the description of an entity. It must therefore be able to uniquely identify the entity in the broadest domain in which it is likely to be used as a pointer or link.The identifier must be able to "stand alone", to uniquely identify the entity in the appropriate domain. Sometimes there are global or universal schemes of identifiers in place, e.g. the ISBN in the global publication world or Australian Company Numbers in Australia. However, for many entities there are no comparable schemes in place. For this reason the identifier element may need to include "domain" information about the broader context of the entity.
Examples

(Note: In the following examples, the elements are expressed in two ways:

  • in the first expression, the context is explicit and detailed in the metadata to ensure unique identification; and
  • in the second expression of the same element, the context is implicit and understood within the domain in which it is applied.

In an ideal world schemes for the identification of domains would be authoritative and enable more concise expression, but in the interests of unique identification, these have been fully spelt out in the examples. The extent of metadata included is an implementation decision. However decision making should take into account the effect on the uniqueness of the identifier, given the intention of this element is for unique identification in the broadest domain in which it will be applied.)

Ambient Function
EITHER
RKMS.Business.Identifier = Commonwealth of Larasutia, CF 4, Defence, 1901/ [National Archives of Larasutia, LRS System (modified 2002)]
OR
(Where the domain of Larasutia and the National Archives of Larasutia are know and implicit)
RKMS.Business.Identifier = CF 4, Defence, 1901/ [National Archives of Larasutia, LRS System (modified 2002)]

EITHERRKMS.Business.Identifier = Commonwealth of Larasutia, Intelligence [Larasutia Government Interactive Functions Thesaurus (2000)]
OR
(Where the domain of Commonwealth of Larasutia is known and implicit)
RKMS.Business.Identifier = Intelligence [LGIFT (2000)]

Business Function
EITHER
RKMS.Business.Identifier = Larasutia, Townhead Council, TCF 46, Financial Management [Townhead Council Records Scheme (1999)]
OR
(Where the domain of Larasutia and Townhead Council are known and implicit)
RKMS.Business.Identifier = TCF 46, Financial Management [Townhead Council Records Scheme (1999)]

Business Activity
EITHER
RKMS.Business.Identifier = Larasutia, Polygon Computers Pty Ltd, 0015 [Polygon Computers Budget Framework (1979)]
OR
(Where the domain of Larasutia, Polygon Computers is known and implicit)
RKMS.Business.Identifier = 0015 [Polygon Computers Budget Framework (1979)]

Business Transaction
EITHER
RKMS.Business.Identifier = Larasutia, Radio Freedom, Program Department 003
OR
(Where domain Larasutia, Radio Freedom, Program department, is known and implicit)
RKMS.Business.Identifier = 003

RKMS03
Entity Switch BUSINESS
Name TITLE
Identifier RKMS.Business.Title
Definition The name of the Business.
Description The name of the business may include a unique identifier, a date and/or function, activity and transaction descriptors drawn from a functional classification scheme or thesaurus. Its data value may be the same as, or incorporate components of the data value for, the Business.Identifier, Business.Date or Business.FunctionalClassification element.
Element Qualifier

May be used to specify type of title, e.g.

  • Main[The "official" or "authorised" name of the entity.]
  • Alternative[Another name by which the entity is known.]
  • Abbreviation
  • Assigned
Value Components

Name
Date

[Specifies time/date/date range when Title valid.]

Scheme

Relevant Schemes
May be used to qualify the whole value of the Business.Title element and the value of the Name Value Component:

  • ABS1220.0 - Australian Standard Classification of Occupations (ASCO) Second Edition (1997)
  • ABS1292.0 - Australian and New Zealand Standard Industrial Classification (ANZSIC) (1992)
  • KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)
  • AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)
Comments  
Examples

Ambient Function
RKMS.Business.Title = Aboriginal Affairs

RKMS.Business.Title = Friendship [Enigma Personal Archives Functions, 2005]

Business Function
RKMS.Business.Title = Name: Personnel Management; Date: 1975/ [RKMS Extension for ISO 8601(2000-03-31)] RKMS.Business.Title.Alternative = Name: Human Resource Management; Date: 1992-1998

RKMS.Business.Title = Support [Enigma Personal Archives Functions, 2005]

Business Activity
RKMS.Business.Title = Aboriginal Affairs; Health Monitoring; Projects [Department of Aboriginal Affairs merged thesaurus (2003-04-12)]

RKMS.Business.Title.Assigned = Strategic Management ProgramRKMS.Business.Title = Name: N93; Equal Employment Opportunity; Date: 1989/ [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS.Business.Title.Abbreviation = EEO

RKMS.Business.Title = Expressing Sympathy [Enigma Personal Archives Functions, 2005]

Business Transaction
RKMS.Business.Title = Loan Application

RKMS.Business.Title = Registration of Reconciliation Pty Ltd

RKMS.Business.Title = Blood Type Test

RKMS.Business.Title = Writing Notes [Enigma Personal Archives Functions, 2005]

RKMS04
Entity Switch BUSINESS
Name DATE
Identifier RKMS.Business.Date
Definition Specifies time/date/date range associated with the business and "life events" relating to it.
Description  
Element Qualifier

May be used to specify type of date, e.g.

  • Executed
  • Implemented
  • Valid
Value Components  
Scheme

Relevant Schemes
May be used to qualify the whole value of the Business.Date element:

ISO 8601 Representation of dates and times (1988-06-15)
DCMI Dublin Core Metadata Initiative Period Encoding Scheme (2000-07-11)

Comments  
Examples

Ambient Function, Business Function, Business Activity
RKMS.Business.Date.Valid = (15 March) 1943-1951 (11 June) [NAL CRS Manual (1992)]

Business Activity
RKMS.Business.Date = 1999-07-04 [ISO8601 (1988-06-15)]

RKSM.Business.Date.Valid = 1949/1953 [RKMS Extension for ISO 8601 (2000-03-31)]
RKMS.Business.Date.Implemented = 1978-04-13/ [RKMS Extension for ISO 8601 (2000-03-31)]

Business Transaction
RKMS.Business.Date.Executed = 1999-07-04T20:30:45+01:00 [ISO8601 (1988-06-15)]

RKMS05
Entity Switch BUSINESS
Name MANDATE
Identifier RKMS.Business.Mandate
Definition Information about the mandate or instrument that provides the legal or administrative basis of the business, governs its execution or authorises related action, which may include its name, unique identifier, date, description and jurisdiction. May be a pointer to a description of the mandate.
Description There are external and internal mandates. Examples of external mandates include laws, regulations, standards or statements of best practice, as well as social mores. Internal mandates include policy, administrative instructions, delegations and authorisations, as well as corporate culture and behaviours.
Element Qualifier

 

Value Components Title [Name of the mandate.]
ID [Unique identifier for mandate.]
Date [Time/date/date range when mandate issued, in place or valid.]
Description [Descriptive text about mandate.]
Jurisdiction [Specification of jurisdiction in which mandate applies.]
Scheme  
Comments  
Examples

Ambient Function, Business Function
EITHER
RKMS.Business.Mandate = Commonwealth of Larasutia, Archives Act, No. 98 of 1983
OR
RKMS.Business.Mandate = Title: Commonwealth of Larasutia, Archives Act, 1983; ID: Commonwealth of Larasutia, Act No. 98 of 1983; Date: 1983-03-14; Definition: an act to regulate recordkeeping in the Commonwealth of Larasutia and its territories; Jurisdiction: Applies to all Commonwealth Agencies as defined in section 46 of Archives Act 1983.

RKMS.Business.Mandate = Title: State of New Zetland, Aborigines Protection Act, 1909; ID: State of Zetland, Act No 25, 1909; Date: 1909-04-13; Description: Aborigines Protection Act; Jurisdiction: New Zetland

Business Activity
RKMS.Business.Mandate = Title: xyz company, Business Plan, 1999; Date: 1999; Description: Business Plan for the xyz company for the years 2000-2002; Jurisdiction: xyz company

RKMS.Business.Mandate = xyz company, Business Plan, 1999

RKMS.Business.Mandate = Title: State of Bliss, Anti Discrimination Act, 1977; Mandate ID: State of Bliss, Act No 64 of 1977; Description: An act outlawing any form of discrimination against citizens of the State of Bliss; Jurisdiction: State of Bliss

Business Transaction
RKMS.Business.Mandate = Title: Distopia, Act No 25 of 2004, Prisoners (Interstate Transfer) Regulation, Schedule 1, Form 1, Request by Prisoner for Transfer to Participating State; ID: Distopia, Act No 25 of 2004, Regulation 63 Schedule 1; Date: 1999 [ISO 8601 (1988-06-15)]; Jurisdiction: Distopia and participating states

RKMS.Business.Mandate = ID: Policy Directive 98/3; Date: 1998; Jurisdiction: xyz company, Freight Division

RKMS06
Entity Switch BUSINESS
Name PLACE
Identifier RKMS.Business.Place
Definition Information about the place associated with the Business.
Description  
Element Qualifier

May be used to specify type of place, e.g.

  • Business Activity Area
  • Service Delivery Point.
Value Components Title [Name of place]
ID [Unique identifier of place.]
Date [Time/date/date range of association with place.]
Scheme

Relevant Scheme
May be used to qualify the whole value of the Business.Place element or the values of the Title and ID Value Components:

ABS1216.0 - Australian Standard Geographical Classification (ASGC) (1998)
ABS1269.0 Standard Australian Classification of Countries (SACC) (1998)
Australian Postcodes, Australia Post (no date)
NAF - Australia Post National Address File (no date)
LCSH - Library of Congress Subject Headings, 22nd edition (1999)
TGN - Getty Thesaurus of Geographic Names, Version 2 (2000-03-14)

Comments  
Examples

Ambient Function
RKMS.Business.Place = 5204, Philippines [LBS 1269.0 Standard Larasutian Classification of Countries (SLCC), revision 2.01 (1999)]

Business Function
RKMS.Business.Place = Tienamin Square

Business Activity
RKMS.Business.Place.ServiceDeliveryPoint = Brown's Newsagency, 15 Dogsbody Rd, Anywhere

RKMS.Business.Place = Title: Colonial Secretary's Building; ID: Bent St, Tatooine; Date: 1810/1945 [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS.Business.Place.BusinessActivityArea = 2000-2999, 1800 [Larasutia Postcodes, Larasutia Post]

RKMS.Business.Place.BusinessActivityArea = Riverina District

RKMS07
Entity Switch BUSINESS
Name FUNCTIONAL CLASSIFICATION
Identifier RKMS.Business.FunctionalClassification
Definition Information about the functional classification of the business in accordance with an authorised source, e.g. a Business or Functional Classification Scheme or Thesaurus.
Description May be a descriptor, a string of descriptors or a hierarchical classification. The classification of the Business entity may also be the name of the entity, or it may include a unique identifier for the entity. Its data value may be the same as, or incorporate components of the data value for, the Business.Identifier or Business.Title elements.
Element Qualifier
  • Ambient Descriptor
  • Functional Descriptor
  • Activity Descriptor
  • Transaction Descriptor
  • Function/Activity Descriptor
  • Activity/Transaction Descriptor
  • Ambient/Functional/Activity/Transaction Descriptor
  • Functional/Activity/Transaction Descriptor
Value Components Descriptor(s) [Term/s taken from the authorised source]
ID [Unique identifier for functional classification.]
Date [Time/date/date range when functional classification applied.]
Description [Descriptive text about functional classification. May include description or scope note from relevant Scheme.]
Scheme

Relevant Schemes
May be used to qualify the value of the Business.FunctionalClassification element, or the values of the Descriptor(s), ID and Description Value Components:

ABS1220.0 - Australian Standard Classification of Occupations (ASCO) Second Edition (1997)
ABS1292.0 - Australian and New Zealand Standard Industrial Classification (ANZSIC) (1992)
KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)
AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)

Comments  
Examples

Ambient Function
RKMS.Business.FunctionalClassification.AmbientDescriptor = Cultural Affairs [NAL Functions thesaurus (1999)]

RKMS.Business.FunctionalClassification.AmbientDescriptor = Law and Order [Bliss State Records, BACAS (2003)]

RKMS.Business.FunctionalClassification.AmbientDescriptor = Memorialising [Enigma Personal Archives, EPA (2005)]

Business Function
RKMS.Business.FunctionalClassification.FunctionalDescriptor = Asset management [Zarathustra, WET Company, functional thesaurus (1994)]

RKMS.Business.FunctionalClassification.FunctionalDescriptor = Interpreting Events [Enigma Personal Archives, EPA (2005)]

Business Activity
RKMS.Business.FunctionalClassification.ActivityDescriptor = Planning [Keyword ZZZ, Rev ed (1998)]; Date: 1999/ [RKMS Extension for ISO 8601 (2000-03-31)]; Description: All acts relating to the preparation, drafting, negotiating and implementation of strategic documents

RKMS.Business.FunctionalClassification. Function/ActivityDescriptor = Health and Aged Care; Access to Health Services; Professional Services Review [Larasutia Budget Appropriation, 2004]

RKMS.Business.FunctionalClassification.ActivityDescriptor = Contemporary Recording [Enigma Personal Archives, EPA (2005)]

Business Transaction
RKMS.Business.FunctionalClassification.TransactionDescriptor = Applying to graduate [Elisian Plains, University of Bogabri thesaurus (1998)]

RKMS.Business.FunctionalClassification.Ambient Descriptor = Community Services - Financial Assistance - Benefit Entitlements [LGIFT Thesaurus (1999)]

RKMS.Business.FunctionalClassification.Functional/Activity/Transaction Descriptor = Insurance Schemes - Compensation / Welfare Programs - Home Benefits Scheme - Applications [Department of Good Things merged thesaurus (1999)]

RKMS.Business.FunctionalClassification.Ambient/Function/Activity/Transaction
Descriptor = Law, Justice and Law Enforcement - Professional Development of Law Practitioners - Adjudication - Justice ForAll [Larasutia Standard Research Classification, 1297.0 (1998)]; ID: 390000-390200-390204; Date: 2004-04-24

RKMS.Business.FunctionalClassification.Activity/TransactionDescriptor = Admissions - Processing [Good Neighbourhood Hospital thesaurus (1998)]

RKMS.Business.FunctionalClassification.TransactionDescriptor = Haemoglobin, Erytholyte sedimentation rate, blood viscosity or more tests [Larasutia Medical Benefits Schedule (1999-11-01, including supplements 2000-02-17 and 2000-05-01)]; ID: Item 65060

RKMS.Business.FunctionalClassification.TransactionDescriptor = Diarising [Enigma Personal Archives, EPA (2005)]

RKMS08
Entity Switch BUSINESS
Name RELATION
Identifier RKMS.Business.Relation
Definition Reference to another entity to which the business is related, and information about the relationship between them.
Description The reference may be to the name and/or unique identifier of the other entity, or it may be a pointer to a description of the other entity.
Element Qualifier  
Value Components

Related To [Use to name, identify or point to the entity to which the Business is related.]
Type [Use to specify Business - Record, Business - Agent, Business - Business, and Business - Business-Recordkeeping relationships.]
Definition [Defines the nature of the relationship between the two entities.]
Date [Date/date range of relationship.]
Mandate [Information about the mandate that authorises or governs the relationship [may include name, ID, date.]
Business Rules [Information about related business rules (may include name, ID, date).]

Scheme

Mandatory Scheme
Use to qualify the whole value of the Type Value Component:

RKMS Category Type Scheme (2000-03-31)

Relevant Scheme
May be used to qualify the value of the for the Definition Value Component:

RKMS Entity Relationships Scheme (under development)

Comments  
Examples

Relation: Business - Business

Ambient Function
For Business Entity Social and Community Services (implicit in the element description)
RKMS.Business.Relation = Related To: Aboriginal Affairs; Type: Ambient Function - Business Function [RKMS Category Type Scheme (2000-03-31)]; Definition: superior in hierarchy; Date: 1979-1994

RMKS.Business.Relation = Related to: Welfare; Type: Ambient Function -Ambient Function [RKMS Category Type Scheme (2000-03-31)]; Definition: successor to; Date: 1965-03-13; Mandate: Commonwealth of Larasutia Order in Council, 1965-03

For Business Entity: Consolidating Identity (implicit in the element description)
RKMS.Business.Relation = Related To: Documenting Relationships; Type: Ambient Function - Business Function [RKMS Category Type Scheme (2000-03-31)]; Definition: superior in hierarchy; Date: 2003/

Business Function
For Personnel Management (implicit in element description)
RKMS.Business.Relation = Related to: Human Resources Management; Type: Business Function - Business Function [RKMS Category Type Scheme (2000-03-31)]; Definition: succeeding; Date: 1994

Business Activity
For Professional Services Review (implicit in element description)
RKMS.Business.Relation = Related to: Health Service Delivery Type: Business Activity - Business Activity [RKMS Category Type Scheme (2000-03-31)]; Definition: preceding; Date: 2006-04-25

Business Transaction
For Professional Development of Law Practitioners - Adjudication - Justice ForAll, ID: 294573 (implicit in element description)
RKMS.Business.Relation = Related to: 340724; Type: Business Transaction -Business Transaction [RKMS Category Type Scheme (2000-03-31)]; Definition: part of; Date: 2004-04-24

Relation: Business - Agent

Ambient Function
For Employment (implicit in element description)
RKMS.Business.Relation = Related To: Department of Community Services; Type: Ambient Function - Organisation/Corporate Body [RKMS Category Type Scheme (2000-03-31)]; Definition: preceding responsible agent; Date: 1996-1998

For Constructing Identity (implicit in element description)
RKMS.Business.Relation = Related To: Biggs Family; Type: Ambient Function - Organisation/Corporate body [RKMS Category Type Scheme (2000-03-31)]; Definition: creator; Date: 1999/

Business Function
RKMS.Business.Relation = inheriting agency from 2049 is http://www.behemoth.com.ze

Business Activity
Business Transaction
For specific transaction implicit in element description
RKMS.Business.Relation = Related To: Sloan Steady; Type: Business Transaction - Person/Actor [RKMS Category Type Scheme (2000-03-31)]; Definition: authorised by; Date: 2031-03-04

Relation: Business - Business-Recordkeeping

Business Activity
For processing grants (implicit in element description)
RKMS.Business.Relation = Related To: Registration [RKMS Business Recordkeeping Functions and Activities Scheme (2000-03-31)]; Type: Business Activity - Business-Recordkeeping Activity; Definition: controlled by; Date: 2003-03-24

For announcement of birth (implicit in element description)
RKMS.Business.Relation = Related To: Transfer [RKMS Business Recordkeeping Functions and Activities Scheme (2000-03-31)]; Type: Business Activity - Business-Recordkeeping Activity; Definition: controlled by; Date: 2010-06-14

RKMS09
Entity Switch BUSINESS
Name ABSTRACT
Identifier RKMS.Business.Abstract
Definition Unstructured textual description of the business.
Description  
Element Qualifier  
Value Components  
Scheme  
Comments This element should not be used to provide information that can be included in other elements.
Examples  

RKMS10
Entity Switch BUSINESS
Name LANGUAGE
Identifier RKMS.Business.Language
Definition Name of language or script in which the business is conducted.
Description  
Element Qualifier  
Value Components  
Scheme

Relevant Schemes
May be used to qualify the whole value of the Business.Language element:

ABS1267.0 -Australian Standard Classification of Languages (ASCL) (1988)
RFC1766 - Tags for Identification of Languages, IMC (Internet Mail Consortium) (1995-03-00)

Comments  
Examples

Ambient Function, Business Function, Business Activity, Business Transaction
RKMS.Business.Language = en [RFC 1766 (1995-03-00)]

RKMS.Business.Language = en-gb [RFC 1766 (1995-03-00)]

RKMS.Business.Language = fr [RFC 1766 (1995-03-00)]

RKMS.Business.Language = ja [RFC 1766 (1995-03-00)]

RKMS11
Entity Switch BUSINESS
Name BUSINESS RULES
Identifier RKMS.Business.BusinessRules
Definition Information about the business rules that specifies how business is conducted. May be a pointer to a description of the business rules or to a system which implements the business rules.
Description Business rules may include business procedures, business process rules and system specifications.
Element Qualifier  
Value Components Title [Name of business rules.]ID[Unique identifier for business rules.]
Date [Time/date/date range when business rules are applicable or valid.]
Description [Descriptive text relating to Business Rules.]
Systems Specifications [System Specifications Value Component may be used to provide information, e.g. identifier, title, date and brief description, about the system specifications for the system that implements the business rules, or a pointer to documentation of the system specifications.]
Scheme  
Comments  
Examples

Business Function
For 'exploration' in a mining company (implicit in element description) RKMS.Business.BusinessRules = Title: Exploration Manual; ID: 98/53; Date: 1998; Description: The Exploration Manual, A Procedure Manual to Stop Rogue Exploration

Business Activity
For 'monitoring market conditions' (implicit in element description)
RKMS.Business.BusinessRules = Title: Marketing Procedures section 3, Market conditions; ID: MDW 31; Date: 1998

Business Transaction
For 'approval of home loans' in a ban k (implicit in element description)
RKMS.Business.BusinessRules = SystemsSpecifications.Title: Bank Processing Workflow System, Superior Systems, version 1.9, workflow design specifications; SystemsSpecification.Date: 2000-01

RKMS.Business.BusinessRules = SystemsSpecification: http://www.harpy.com/systems/procedures/1997/version3.html

RKMS12
Entity Switch BUSINESS-RECORDKEEPING
Name CATEGORY TYPE
Identifier RKMS.BusinessRecordkeeping.CategoryType
Definition Name of type of Business-Recordkeeping entity.
Description This element identifies the type of business-recordkeeping entity being described with reference to the Transactional Axis of the Records Continuum Model. Business-Recordkeeping entities include classes of recordkeeping business transactions, recordkeeping business activities, recordkeeping business functions and recordkeeping ambient functions (broad societal purposes). The Category Type element is intended to function as a handshake or introduction for the metadata record, e.g.: "Hello, I'm a description of a recordkeeping business activity."
Element Qualifier  
Value Components  
Scheme

Mandatory Scheme
Use to qualify the whole value of the BusinessRecordkeeping.CategoryType element:

RKMS Category Type Scheme (2000-03-31)

Comments  
Examples

Business-Recordkeeping Ambient Function
RKMS.BusinessRecordkeeping.CategoryType = Business-Recordkeeping Ambient Function [RKMS Category Type Scheme, (2000-03-31)]

Business-Recordkeeping Function
RKMS.BusinessRecordkeeping.CategoryType = Business-Recordkeeping Function [RKMS Category Type Scheme, (2000-03-31)]

Business-Recordkeeping Activity
RKMS.BusinessRecordkeeping.CategoryType = Business-Recordkeeping Activity [RKMS Category Type Scheme, (2000-03-31)]

Business-Recordkeeping Transaction
RKMS.BusinessRecordkeeping.CategoryType = Business-Recordkeeping Transaction [RKMS Category Type Scheme, (2000-03-31)]

RKMS13
Entity Switch BUSINESS-RECORDKEEPING
Name IDENTIFIER
Identifier RKMS.BusinessRecordkeeping.Identifier
Definition A unique identifier assigned to the recordkeeping business within a particular domain.
Description The unique identifier may include the name of the recordkeeping business, a date associated with the recordkeeping business, and/or function, activity and transaction descriptors drawn from a functional classification scheme or thesaurus. Its data value may be the same as, or incorporate components of the data value for the BusinessRecordkeeping.Title, BusinessRecordkeeping.Date or BusinessRecordkeeping.Functional Classification element.
Element Qualifier  
Value Components  
Scheme

Relevant Schemes
May be used for BusinessRecordkeeping.Identifier element:

RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)
KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)
AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)

Comments One important use of this element is to point or provide a link to the description of an entity. It must therefore be able to uniquely identify the entity in the broadest domain in which it is likely to be used as a pointer or link.The identifier must be able to "stand alone", to uniquely identify the entity in the appropriate domain. Sometimes there are global or universal schemes of identifiers in place, e.g. the ISBN in the global publication world or Australian Company Numbers in Australia. However, for many entities there are no comparable schemes in place. For this reason the identifier element may need to include "domain" information about the broader context of the entity.
Examples

(Note: In the following examples, the elements are expressed in two ways:

  • in the first expression, the context is explicit and detailed in the metadata to ensure unique identification; and
  • in the second expression of the same element, the context is implicit and understood within the domain in which it is applied.

In an ideal world schemes for the identification of domains would be authoritative and enable more concise expression, but in the interests of unique identification, these have been fully spelt out in the examples. The extent of metadata included is an implementation decision. However decision making should take into account the effect on the uniqueness of the identifier, given the intention of this element is for unique identification in the broadest domain in which it will be applied.)

Business-Recordkeeping Ambient Function
EITHER
RKMS.BusinessRecordkeeping.Identifier = Commonwealth of Larasutia, LF 10 [National Archives of Larasutia, Functions Thesaurus (2001)]
OR
(Where the domain of Larasutia is known and implicit)
RKMS.BusinessRecordkeeping.Identifier = LF10 [National Archives of Larasutia, Functions Thesaurus (2001)]

Business-Recordkeeping Function
EITHER
RKMS.BusinessRecordkeeping.Identifier = Larasutia, Enzymes-R-Us Pty Ltd, AF 352 [Enzymes-R-Us Pty Ltd, Recordkeeping Program Budget Structure (2003)]
OR
(Where the domain of Larasutia, Enzymes-R-Us company, Recordkeeping Program is known and implicit)
RKMS.BusinessRecordkeeping.Identifier = AF 352

Business-Recordkeeping Activity
EITHER
RKMS.BusinessRecordkeeping.Identifier = Larasutia, State of Bliss, Regional Archives of Callista, CAF 436, Access - Permissions [Regional Archives of Callista, Recordkeeping Control System (2000)]
OR
(Where the domain of Larasutia, State of Bliss, Regional Archives of Callista is known and implicit)
RKMS.BusinessRecordkeeping.Identifier = CAF 436, Access - Permissions [Recordkeeping Control System (2000)]

RKMS14
Entity Switch BUSINESS-RECORDKEEPING
Name TITLE
Identifier RKMS.BusinessRecordkeeping.Title
Definition The name of the recordkeeping business.
Description The name of the recordkeeping business may include a unique identifier, date and/or function, activity and transaction descriptors drawn from a functional classification scheme or thesaurus. Its data value may be the same as, or incorporate components of the data value for, the BusinessRecordkeeping.Identifier, BusinessRecordkeeping.Date or BusinessRecordkeeping.Functional Classification element.
Element Qualifier

May be used to specify the type of title, e.g.

  • Main
    [The "official" or "authorised" name of the entity.]
  • Alternative
    [Another name by which the entity is known.]
  • Abbreviation
  • Assigned
Value Components Name
Date [Specifies time/date/date range when Title valid.]
Scheme

Relevant Schemes
May be used to qualify the whole value of the BusinessRecordkeeping.Title element and the value of the Name Value Component:

RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)
KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)
AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)

Comments  
Examples

Business-Recordkeeping Ambient Function
RKMS.BusinessRecordkeeping.Title = Authentication

Business-Recordkeeping Function
RKMS.BusinessRecordkeeping.Title.Main = Appraisal [RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)]
RKMS.BusinessRecordkeeping.Title.Alternative = Disposition

Business-Recordkeeping Activity
RKMS.BusinessRecordkeeping.Title = Requirements Definition
RKMS.BusinessRecordkeeping.Title.Abbreviation = RKReqDef

RKMS.BusinessRecordkeeping.Title = Tracking; Date: 1992-1999
RKMS.BusinessRecordkeeping.Title = Context Description; Date: 1999/ [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS.BusinessRecordkeeping.Title = Conservation [RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)]

RKMS.BusinessRecordkeeping.Title = Disposal [RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)]Title.Alternative = Disposition

RKMS15
Entity Switch BUSINESS-RECORDKEEPING
Name DATE
Identifier RKMS.BusinessRecordkeeping.Date
Definition Specifies time/date/date range of recordkeeping business or "life events" relating to it.
Description  
Element Qualifier

Element qualifier may be used specify type of Date, e.g.

  • Executed
  • Implemented
  • Valid
Value Components  
Scheme

Relevant Schemes
May be used to qualify the whole value of the BusinessRecordkeeping.Date element:

ISO 8601 Representation of dates and times (1988-06-15)
RKMS Extension for ISO 8601 (2000-03-31)

Comments  
Examples

RKMS.BusinessRecordkeeping.Date = 1997-03 [ISO 8601 (1988-06-15)]

RKMS.BusinessRecordkeeping.Date.Executed = 1999-07-10 [ISO 8601 (1988-06-15)]

RKMS.BusinessRecordkeeping.Date.Valid = 1997-03-25/ [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS.BusinessRecordkeeping.Date.Implemented = 1998

RKMS16
Entity Switch BUSINESS-RECORDKEEPING
Name MANDATE
Identifier RKMS.BusinessRecordkeeping.Mandate
Definition Information about the mandate or instrument that provides the legal or administrative basis of the recordkeeping business, governs its execution or authorises related action, which may include its name, unique identifier, date, description and jurisdiction. May be a pointer to a description of the mandate.
Description There are external and internal mandates. Examples of external mandates include laws, regulations, standards or statements of best practice, as well as social mores. Internal mandates include policy, administrative instructions, delegations and authorisations, as well as corporate culture and behaviours.
Element Qualifier  
Value Components Title [Name of the mandate.]
ID [Unique identifier for mandate.]
Date [Time/date/date range when mandate issued, in place or valid.]
Description [Descriptive text about mandate.]
Jurisdiction [Specification of jurisdiction in which mandate applies.]
Scheme  
Comments  
Examples

Business-Recordkeeping Ambient Function
RKMS.BusinessRecordkeeping.Mandate = Commonwealth of Larasutia, Archives Act, No. 98 of 1983

RKMS.BusinessRecordkeeping.Mandate = Title: Commonwealth of Larasutia, Archives Act, 1983; ID: Commonwealth of Larasutia, Act No. 98 of 1983; Date: 1983-03-14; Definition: an act to regulate recordkeeping in the Commonwealth of Larasutia and its territories; Jurisdiction: Applies to all Commonwealth Agencies as defined in section 46 of Archives Act 1983.

RKMS.BusinessRecordkeeping.Mandate = Title: State of Middling Importance, Recordkeeping Act, 1999; ID: State of Middling Importance Act No 63 of 1999; Date: 1999-05-25 [ISO 8601 (1988-06-15)]; Description: an act to establish mandatory requirements relevant to those government agencies working within the ambit of Middling Importance jurisdiction; Jurisdiction: State of Middling Importance government agencies, extending to private companies employed in the administration of outsourced recordkeeping arrangements for State of Middling Importance agencies.

Business-Recordkeeping Function
RKMS.BusinessRecordkeeping.Mandate = Title: AS 4390, Australian Standard on Records Management, 1996; ID: AS 4390; Date: 1999-02-25

RKMS.BusinessRecordkeeping.Mandate = AS 4390, Australian Standard on Records Management, 1996. Part 4, Control

Business-Recordkeeping Activity
RKMS.BusinessRecordkeeping.Mandate = Title: Recordkeeping Policy; ID: 99/153; Date: 1999-04-23; Description: corporate policy on recordkeeping for Microhard Pty Ltd adopted by the Board on April 23rd 1999.

Business-Recordkeeping Transaction
RKMS.BusinessRecordkeeping.Mandate = Title: Standard on Email use and management; ID: S1934; Date: 1999-06-25; Jurisdiction: Dustbusters Pty Ltd and subsidiary companies.

RKMS17
Entity Switch BUSINESS-RECORDKEEPING
Name PLACE
Identifier RKMS.BusinessRecordkeeping.Place
Definition Information about the place associated with the recordkeeping business.
Description  
Element Qualifier

May be used to specify type of place, e.g.

  • Business Activity Area
  • Service Delivery Point.
Value Components Title [Name of place]
ID [Specifies ID of place.]
Date [Specifies time/date/date range of association with place.]
(Note: May be used with Element and Element Qualifiers.)
Scheme

Relevant Schemes
May be used to qualify the whole value of the BusinessRecordkeeping.Place element and the values of the Title and ID Value Components:

ABS1216.0 - Australian Standard Geographical Classification (ASGC) (1998)
ABS1269.0 - Standard Australian Classification of Countries (SACC) (1998)
Australian Postcodes, Australia Post (no date)
NAF - Australia Post National Address File (no date)
LCSH - Library of Congress Subject Headings, 22nd edition (1999)
TGN - Getty Thesaurus of Geographic Names, Version 2 (2000-03-14)

Comments  
Examples

Business-Recordkeeping Function
RKMS.BusinessRecordkeeping.Place = Mierendorffstrasse 16, 10589 Berlin-Charlottenburg

RKMS.BusinessRecordkeeping.Place = 5206, East Timor [LBS 1269.0 Standard Larasutian Classification of Countries (SACC) (1998, Revision 2.01 2000)]
RKMS.BusinessRecordkeeping.Place = Australian Embassy, Dili

Business-Recordkeeping Activity
RKMS.BusinessRecordkeeping.Place = Title: Recordkeeping Program; ID: Budget Unit 246; Date: 2006-02/ [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS.BusinessRecordkeeping.Place.ServiceDeliveryPoint = Recordkeeping Unit, Level 7, 129 Elephantine Street, Wingera

RKMS.BusinessRecordkeeping.Place.BusinessActivityArea = Carboolshire District; Date: 1978-1983

RKMS.BusinessRecordkeeping.Place.BusinessActivityArea = Kooroongarra, Qld, 4357 [Larasutian Postcodes, Larasutia Post (no date)]

RKMS18
Entity Switch BUSINESS-RECORDKEEPING
Name FUNCTIONAL CLASSIFICATION
Identifier RKMS.BusinessRecordkeeping.FunctionalClassification
Definition Information about the functional classification of the recordkeeping business in accordance with an authorised source, e.g. a Business or Functional Classification Scheme or Thesaurus.
Description May be a string of descriptors or a hierarchical classification. The classification of the Business-Recordkeeping entity may also be the name of the entity, or it may include a unique identifier for the entity. Its data value may be the same as, or incorporate components of the data value for, the BusinessRecordkeeping.Title or BusinessRecordkeeping.Functional Classification element.
Element Qualifier
  • Ambient Descriptor
  • Functional Descriptor
  • Activity Descriptor
  • Transaction Descriptor
  • Function/Activity Descriptor
  • Activity/Transaction Descriptor
  • Ambient/Functional/Activity/Transaction Descriptor
  • Functional/Activity/Transaction Descriptor
Value Components Descriptor(s) [Term/s taken from the authorised source]
ID [Unique identifier for functional classification.]
Date [Time/date/date range when functional classification applied.]
Description [Descriptive text about functional classification. May include description or scope note from relevant Scheme.]
Scheme

Relevant Schemes
May be used to qualify the whole value of the BusinessRecordkeeping.Functional Classification element and the values of the Descriptor(s), ID and Description Value Components:

RKMS Business-Recordkeeping Functions and Activities Scheme (2000-03-31)
KAAA - Keyword AAA Thesaurus of General Terms (1998 revised)
AGIFT - Australian Government Interactive Functions Thesaurus (1999-11-26)

Comments  
Examples

Business-Recordkeeping Ambient Function
RKMS.BusinessRecordkeeping.FunctionalClassification.AmbientDescriptor = Descriptor: Cultural Affairs [LGIFT (1999-10)]; ID: L152; Date: 1999/2000-02
RKMS.BusinessRecordkeeping.FunctionalClassification.AmbientDescriptor = Descriptor: Heritage [LGIFT (1999, revised 2000)]; ID L243; Date: 2000-02-28/ [RKMS Extension for ISO 8601 (2000-03-31)]

Business-Recordkeeping Function
RKMS.BusinessRecordkeeping.FunctionalClassification.FunctionalDescriptor= Information Management [Keyword ZZZ, rev ed (1998)]

Business-Recordkeeping Activity
RKMS.BusinessRecordkeeping.FunctionalClassification.ActivityDescriptor = Conservation [Keyword ZZZ, rev ed (1998)]

Business-Recordkeeping Transaction
RKMS.Business.Recordkeeping.FunctionalClassification.AmbientDescriptor = Communications [LGIFT (1999-10)];
RKMS.Business.Recordkeeping.FunctionalClassification. Functional/Activity/Transaction Descriptor =Information Management - Standards - Records [Keyword ZZZ, rev ed (1998)]

RKMS.Business.Recordkeeping.FunctionalClassification.Functional/Activity/
TransactionDescriptor = Records Management - Disposal - Decisions [Inspect Mining Functional Thesaurus (1996)]

RKMS19
Entity Switch BUSINESS-RECORDKEEPING
Name RELATION
Identifier RKMS.BusinessRecordkeeping.Relation
Definition Reference to another entity to which the Business-Recordkeeping entity is related, and information about the relationship between them.
Description The reference may be to the name and/or unique identifier of the other entity, or it may be a pointer to a description of the other entity.
Element Qualifier  
Value Components Related To [Use to name, identify or point to the entity to which the Business-Recordkeeping entity is related.]
Type [Use to specify Business-Recordkeeping - Record, Business-Recordkeeping - Agent, Business-Recordkeeping - Business, and Business-Recordkeeping - Business-Recordkeeping relationships.]
Definition [Provides information about nature of relationship between entities.]
Date [Date/date range of relationship.]
Mandate [Information about mandate that authorises or governs relationship (may include identifier, title, date).]
Business Rules [Information about related business rules (may include identifier, title, date).]
Scheme

Mandatory Scheme
Use to qualify the Type Value Component:

RKMS Category Type Scheme (2000-03-31)

Relevant Scheme
May be used to qualify the Definition Value Component:

RKMS Entity Relationships Scheme (under development)

Comments  
Examples

Business-Recordkeeping - Record

Business-Recordkeeping Activity
For 'disposal' (implicit in element description)
EITHER
RKMS.BusinessRecordkeeping.Relation = Related To: TR2, Correspondence Files; Type: Business-Recordkeeping Activity - Record Aggregation [RKMS Category Type Scheme (2000-03-31)]; Definition: documented in; Date: 1973/
OR
RKMS.BusinessRecordkeeping.Relation = documented in TR2 Correspondence Files, 1973/

Business-Recordkeeping - Business

Business-Recordkeeping Business Activity
For 'Establishing Recordkeeping Requirements' (implicit in element description)
RKMS.BusinessRecordkeeping.Relation = Related To: Community Services -Community Support - Child and Youth Support [LGIFT (1999-10)]; Type: Business-Recordkeeping Activity - Business Activity [RKMS Category Type Scheme (2000-03-31)]; Definition: provides evidence of; Date: 1999-04-15 [ISO 8601 (1988-06-15)]

Business-Recordkeeping - Agent

Business-Recordkeeping Ambient Function
For 'Authentication' (implicit in element description)
RKMS.BusinessRecordkeeping.Relation = Related To: National Archives of Larasutia; Type: Recordkeeping Ambient Function - Organisation/Corporate Body [RKMS Category Type Scheme (2000-03-31)]; Definition: responsible for; Date: 1999; Mandate: Commonwealth of Larasutia, Archives Act, No. 98 of 1983

Business-Recordkeeping Function
For 'Appraisal' (implicit in element description)
RKMS.BusinessRecordkeeping.Relation = Related To: Recordkeeping Unit; Type: Business-Recordkeeping Function - Organisational Unit/Work Group [RKMS Category Type Scheme (2000-03-31)]; Definition: responsible for; Date: 1992-03 [ISO 8601 (1988-06-15)]RKMS.BusinessRecordkeeping.Relation = http://www.kensington.com.au/corporateservices/recordkeepingunit.html

Business-Recordkeeping - Business-Recordkeeping

Business-Recordkeeping Function
For 'Appraisal' (implicit in element description)
RKMS.BusinessRecordkeeping.Relation = Establishing Recordkeeping Requirement; Type: Recordkeeping Business Function - Recordkeeping Business Activity [RKMS Category Type Scheme (2000-03-31)]; Definition: Part of; Date:1999-02-08/ [RKMS Extension for ISO 8601 (2000-03-31)]

RKMS20
Entity Switch BUSINESS-RECORDKEEPING
Name ABSTRACT
Identifier RKMS.BusinessRecordkeeping.Abstract
Definition Unstructured textual description of the recordkeeping business.
Description  
Element Qualifier  
Value Components  
Scheme  
Comments This element should not be used to provide information that can be included in other elements
Examples

Business-Recordkeeping Business Function
(Where the business-recordkeeping function 'Appraisal' is implicit in element description)
RKMS.BusinessRecordkeeping.Abstract = Appraisal is the business function documenting all processes associated with determining which records need to be captured and how long the records need to be kept to meet business needs, the requirements of organisational accountability and community expectations

Business-Recordkeeping Business Activity
(Where the business-recordkeeping activity ' rendering' is implicit in element description)
RKMS.BusinessRecordkeeping.Abstract = Rendering is the business activity associated with specifying all technical and implementation parameters for enabling records to be re-presented in an appropriate form

RKMS21
Entity Switch BUSINESS-RECORDKEEPING
Name LANGUAGE
Identifier RKMS.BusinessRecordkeeping.Language
Definition Specification of language or script in which the recordkeeping business is done.
Description  
Element Qualifier  
Value Components  
Scheme

Relevant Schemes
May be used to qualify the whole value of the Business.Language element:

ABS1267.0 - Australian Standard Classification of Languages (ASCL) (1988)
RFC1766 - Tags for Identification of Languages, IMC (Internet Mail Consortium) (1995-03-00)

Comments  
Examples

Business-Recordkeeping Ambient Function, Business-Recordkeeping Business Function, Business-Recordkeeping Activities, Business-Recordkeeping Transaction

RKMS.BusinessRecordkeeping.Language = en [RFC 1766 (1995-03-00)]

RKMS.BusinessRecordkeeping.Language = en-au [RFC 1766 (1995-03-00)]

RKMS.BusinessRecordkeeping.Language = vi [RFC 1766 (1995-03-00)]

RKMS22
Entity Switch BUSINESS-RECORDKEEPING
Name BUSINESS RULES
Identifier RKMS.BusinessRecordkeeping.BusinessRules
Definition Information about the business rules that specify how recordkeeping business is conducted. May be a pointer to a description of the business rules or to a system which implements the business rules.
Description Business rules may include business procedures, business process rules and system specifications.
Element Qualifier  
Value Components Title [Name of business rules.]
ID [Unique identifier for business rules.]
Date [Time/date/date range when business rules are applicable or valid.]
Description [Descriptive text relating to Business Rules.]
Systems Specifications [System Specifications Value Component may be used to provide information, e.g. identifier, title, date or brief description, about the system specifications for the system that implements the business rules, or a pointer to documentation of the system specifications.]
Scheme

 

Comments  
Examples

Business-Recordkeeping Function
For 'Appraisal' (implicit in element description)
RKMS.BusinessRecordkeeping.BusinessRules = Title: DURKS Manual, section 4.3.1; ID: Draft February 2000, section 4.3.1; Date: 2000-02; Description: This section of the manual refers to business rules for appraisal adopted by Teleban Company.

RKMS.BusinessRecordkeeping.BusinessRules = http://www.records.com/DURKSmanual/sect4.html

For 'Access' (implicit in element description)
RKMS.BusinessRecordkeeping.BusinessRules = Title: Rules governing application of ASP program Administering Access by Records Gurus; Date: 2006-04-15/2009-06-14 [ISO 8601 (1988-06-15)]; Systems Specification: http://www.recordsgurus.com.au/accessasp.html

Business-Recordkeeping Activity
For 'Indexing' (implicit in element description)
RKMS.BusinessRecordkeeping.BusinessRules = Date: 1999-02-12; Systems Specifications: RecBind Corporate 32, November 1999 release

For 'Registration' (implicit in element description)
RKMS.BusinessRecordkeeping.BusinessRules = all paper and electronic transactions will be individually registered within the records system on receipt, 1998-09

Business-Recordkeeping Transaction
RKMS.BusinessRecordkeeping.BusinessRule = Title: Email Rules; Date: 1998; Description: Every transaction sent through email will be registered into the records system; System Specification: Objectiff 2000

RKMS23
Entity Switch AGENTS [PEOPLE]
Name CATEGORY TYPE
Identifier RKMS.Agents.CategoryType
Definition Name of type of Agent entity
Description This element identifies the type of agents being described with reference to the Identity Axis of the Records Continuum Model. Agents include persons or actors, collaborative groups or organisational units, organisations or corporate bodies, and social institutions. The Category Type element is intended to function as a handshake or introduction for the metadata record, e.g.: "Hello, I'm a description of an organisation."
Element Qualifier  
Value Components  
Scheme

Mandatory Scheme
Use to qualify the whole value of the Agents.CategoryType element:

RKMS Category Type Scheme (2000-03-31)

Comments  
Examples

Social Institution
RKMS.Agents.CategoryType = Social Institution [RKMS Category Type Scheme (2000-03-31)]

Organisation/Corporate Body
RKMS.Agents.CategoryType = Organisation/Corporate Body [RKMS Category Type Scheme (2000-03-31)]

Organisational Unit/Work Unit
RKMS.Agents.CategoryType = Organisational Unit/Work Unit [RKMS Category Type Scheme (2000-03-31)]

Person/Actor
RKMS.Agents.CategoryType = Person/Actor [RKMS Category Type Scheme (2000-03-31)]

RKMS24
Entity Switch AGENTS [PEOPLE]
Name IDENTIFIER
Identifier RKMS.Agents.Identifier
Definition A unique identifier assigned to the Agent within a particular domain.
Description The unique identifier may include the name or a date associated with the agent. Its data value may be the same as, or incorporate components of the data value for, the Agents.Title and Agents.Date elements.
Element Qualifier  
Value Components  
Scheme

Relevant Schemes
May be used to qualify the whole value of the Agents.Identifier element:

ABN - Australian Business Number (1999-11-01)
ACN - Australian Company Number (1991-01-01)
AGS Number, Australian Government Service Number (no date)
ARBN - Australian Registered Body Number (1991-01-01)
Registers for Commonwealth Organisations (CO) and Commonwealth Agencies (CA), National Archives of Australia (?1966/ )
RFC2426 - vCard MIME Directory Profile, IMC (Internet Mail Consortium) (1998-09-00)

Comments One important use of this element is to point or provide a link to the description of an entity. It must therefore be able to uniquely identify the entity in the broadest domain in which it is likely to be used as a pointer or link.The identifier must be able to "stand alone", to uniquely identify the entity in the appropriate domain. Sometimes there are global or universal schemes of identifiers in place, e.g. the ISBN in the global publication world or Australian Company Numbers in Australia. However, for many entities there are no comparable schemes in place. For this reason the identifier element may need to include "domain" information about the broader context of the entity.
Examples

(Note: In the following examples, the elements are expressed in two ways:

  • in the first expression, the context is explicit and detailed in the metadata to ensure unique identification; and
  • in the second expression of the same element, the context is implicit and understood within the domain in which it is applied.

In an ideal world schemes for the identification of domains would be authoritative and enable more concise expression, but in the interests of unique identification, these have been fully spelt out in the examples. The extent of metadata included is an implementation decision. However decision making should take into account the effect on the uniqueness of the identifier, given the intention of this element is for unique identification in the broadest domain in which it will be applied.)

Social Institution or Organisation/Corporate Body
EITHER
RKMS.Agents.Identifier = Commonwealth of Larasutia, CO 145 [Register of Commonwealth Organisations, National Archives of Larasutia (1997)]
OR
(Where the domain of the Commonwealth of Larasutia is known and implicit)
RKMS.Agents.Identifier = CO 145 [Register of Commonwealth Organisations, National Archives of Larasutia (1997)]

Organisation/Corporate Body
EITHER
RKMS.Agents.Identifier = Commonwealth of Larasutia, CA 8937, Department of Emotional Wellbeing [Register of Commonwealth Agencies, National Archives of Larasutia (1997)]
OR
(Where the domain of the Commonwealth of Larasutia is known and implicit)
RKMS.Agents.Identifier = CA 8937, Department of Emotional Wellbeing [Register of Commonwealth Agencies, National Archives of Larasutia (1997)]

EITHER
RKMS.Agents.Identifier = State of Bliss, 235 [State of Bliss, Agency Registration System (1999)]
OR
(Where the domain of the State of Bliss is known and implicit)
RKMS.Agents.Identifier = 235 [State of Bliss, Agency Registration System (1999)]

EITHER
RKMS.Agents.Identifier = Larasutia, LCN 085 801 743 [Larasutian Company Registration Number (1999)]
OR
(Where the domain of Larasutia is known and implicit)
RKMS.Agents.Identifier = LCN 085 801 743 [Larasutian Company Registration Number (1999)]

EITHER
RKMS.Agents.Identifier = Larasutia, LBN 63 058 934 734 [Larasutian Business Number (2000)]
OR
(Where the domain of Larasutia is known and implicit)
RKMS.Agents.Identifier = LBN 63 058 934 734 [Larasutian Business Number (2000)]

Organisation/Corporate Body or Person as entity
EITHER
RKMS.Agents.Identifier = Larasutia, LTN 121 643 964, Sisters of Divine Right [Larasutian Taxation Office, registered tax number]
OR
(Where the domain of Larasutia is known and implicit)
RKMS.Agents.Identifier = LTN 121 643 964, Sisters of Divine Right [Larasutian Taxation Office, registered tax number]

Organisational Unit/Work Group
EITHER
RKMS.Agents.Identifier = Larasutia, Get Rich Quick Company 00263 [Get Rich Quick Company, Budgetary Unit Number (1964)]
OR
(Where the domain of Larasutia, Get Rick Quick company is known and implicit)
RKMS.Agents.Identifier = 00263 [Get Rich Quick Company, Budgetary Unit Number (1964)]

Person/Actor
EITHER
RKMS.Agents.Identifier = Larasutia, Bermagui Fruit Cooperative, 198365, Hieronymous Nouveau [Bermagui Fruit Cooperative, Employee number (1994)]
OR
(Where the domain of Larasutia, Bermagui Fruit Cooperative is known and implicit)
RKMS.Agents.Identifier = 198365, Hieronymous Nouveau [Bermagui Fruit Cooperative, Employee number (1994)]

RKMS25
Entity Switch AGENTS [PEOPLE]
Name TITLE
Identifier RKMS.Agents.Title
Definition The name of the Agent.
Description The name of the agent may include a unique identifier or date. Its data value may be the same as, or incorporate components of the data value for, the Agents.Identifier and Agent.Date.
Element Qualifier

May be used to specify type of title, e.g.

  • Main
  • Alternative
  • Abbreviation
  • Assigned
Value Components Name
Date [Specifies time/date/date range when Title valid.]
(Note: May be used with Element and Element Qualifiers.)
Scheme

Relevant Schemes
May be used to qualify the whole value of the Agent.Title element:

AACR - Anglo-American Cataloguing Rules, (1998)
ABN - Australian Business Number (1999-11-01)
ACN - Australian Company Number Registration (1991-01-01)
ARBN - Australian Registered Body Number (1991-01-01)
Registers for Commonwealth Organisations (CO) and Commonwealth Agencies (CA), National Archives of Australia (?1966/ )
RFC2426 - vCard MIME Directory Profile, IMC (Internet Mail Consortium) (1998-09-00)

Comments  
Examples

Social Institution
RKMS.Agents.Title = Ron Smith
RKMS.Agents.Title.Alternative = Percifal the Magician

Organisation/Corporate Body
RKMS.Agents.Title = Larasutia Bureau of Meteorology, Head Office
RKMS.Agents.Title.Alternative = Bureau of Meteorology

RKMS.Agents.Title = Name: Department of the Environment [II] [LRS Manual (1997)]; Date: 1973-1983
RKMS.Agents.Title = Name: Department of the Environment [III] [LRS Manual (1