Embed Size (px)
Citation preview
The Domesday Book "dom", oznacza w
staroangielskim zliczanie – czyli "dzień obrachunku";
Dzień Sądu Ostatecznego, będący dniem "rozliczenia"
Domesday book• Books compiled between January 1086
and September 1087• Average of 44 lines of writing per page• Some 200 sheep died to make Little
Domesday book• Whole value of places surveyed was
£78,000 - value today is £3 trillion• Book can still be used today in court for
property disputes
• Domesday was originally kept with the royal treasury at Winchester.
• But from the early 13th century, when it was not travelling around with the King, it was housed in Westminster at first in the palace and then in the abbey.
• From about 1600 it was kept in a large iron-clad chest and reinforced with iron straps. The chest had three different locks, the keys to which were divided between three different officials, so that it could only be opened by consent of all three.
• In 1859 Domesday was removed to the new Public Record Office in Chancery Lane, London. In 1996 it was brought to The National Archives, Kew.
Kto to spisał? • Ranulf Flambard (sometimes Ralph
Flambard, Ranulph Flambard, or Ranulf Passiflamme; c. 1060 – 5 September 1128) was a medieval Norman Bishop of Durham and an influential government minister of King William Rufus of England. Ranulf was the son of a priest of Bayeux, Normandy, and his nickname Flambard means incendiary or torch-bearer, and may have referred to his personality. He started his career under King William I of England, probably in the compilation of the Domesday Book, as well as being the keeper of the king's seal. On the death of William I, Ranulf chose to serve the new king of England, William Rufus.
• The Domesday Book (1086) entry for Keighley reads "In Chichelai, Ulchel and Thole and Ravensuar and William had six carucates to be taxed" (a carucate is the farmland which could be cultivated with one plough and a team of eight oxen in a year: 100 - 120 acres). The Old English name Chichelai means that Cyhha, an Anglo-Saxon thane, had originally cultivated a forest clearing (-ley). Domesday tells us that William was also taxed on a carucate in Utley (Utta's clearing) and another at Newsholme (new houses); he and Gamelbar shared another at Oakworth (oak-tree enclosure); Gamelbar held another three at Wilsden (Wifel's valley); Ravensuar also held two at Laycock (small stream); Ardulf, one at Riddelesden (Rethel's valley), four at Morton (moorland farmstead) and half at Hainworth (Hagena's enclosure); Ernegis had half a carucate at Hainworth and one at Marley (a clearing frequented by martens)... "and they are waste" referring to William the Conqueror''s harrying of the North after a failed revolt.
The BBC Domesday Project - November 1986
• http://www.domesday.org.uk/
A Domesday system at the VCF-GB 2010
Adrian Pearce• If you are looking for the on-line version of
the 1986 BBC Domesday produced by Adrian Pearce, sadly it is no longer available.
Domesday 25th Anniversary Event
• Submitted by Darren Grant on Mon, 12/12/2011 - 11:42pm
• A new BBC Domesday multi-media touchtable has been unveiled at The National Museum of Computing (TNMOC) to celebrate the 25th anniversary of the BBC Domesday project, and the completion of the 2011 Domesday Reloaded project. Peter Armstrong, who led the original project gave a short speech about the project and the new table in the video below.
http://www.bbc.co.uk/history/domesday
Functional Requirements for Electronic Records Management Systems
• The National Archives updated the functional requirements for electronic records management systems (ERMS) in collaboration with the central government records management community during 2002.
• The revision takes account of developments in cross-government and international standards since 1999.
Functional Requirements for Electronic Records Management Systems
• requirements emerging from work to implement recent legislation in dataprotection and freedom of information
• experience from clarifying and elucidating the first version of requirements to government staff and software suppliers
• EU Model Requirements for ERM systems (MoReq)
• experience in testing software applications• lessons shared by international experience
Level of requirement• mandatory requirements are indicated by
the phrase “The ERMS must...”• highly desirable requirements are
indicated by the phrase “The ERMS should...”
• desirable requirements are indicated by the phrase “The ERMS may ...”.
Structure of requirements• A core requirements
– build and maintain a classification scheme, against which folders are classified
– manage folders, parts and records, and their metadata– declare an electronic document as a corporate record, and to maintain its
integrity as an authentic representation of a business action or decision– search for and retrieve records– consistently manage the retention and disposition of whole folders and
records,– retaining what should be kept and disposing of what should not, whether
by transfer to another organisation or destruction– control access to folders and records, and to maintain an auditable track
of actions taken on them– provide manageable, usable and robust mechanisms to carry out core
functions• B optional modules
– Content management and ERM– Casework and workflow– Image management and document scanning– Preparing records for transfer
Structure of requirements• A . 1 : RECORD ORGANISATION• A. 2 : RECORD CAPTURE, DECLARATION AND
MANAGEMENT• A. 3 : SEARCH, DISPLAY AND PRESENTATION• A. 4 : RETENTION AND DISPOSAL• A. 5. ACCESS CONTROL• A. 6. AUDIT• A. 7. REPORTING• A. 8 : USABILITY• A. 9 : DESIGN AND PERFORMANCE• A. 10 : COMPLIANCE WITH OTHER STANDARDS
A . 1 : RECORD ORGANISATION
• Classification scheme and fileplan• Class metadata• Folders• Folder metadata• Folder management• Parts(68 wymagań)
Folders• A.1.25 (M) Where a hierarchical classification scheme is in
use, the ERMS must allow the addition of folders to only the lowest level class in any single part of the scheme.
• A.1.26 (HD) The ERMS should support an optional class and folder structured naming mechanism which includes names (e.g. personal or corporate names) and dates (e.g. dates of birth) as elements of the class and folder name.
• A.1.27 (HD) When creating a new electronic folder in a classification scheme which uses a structured numerical or alphanumerical reference, the ERMS should automatically generate the next sequential number available at that position within the scheme.
• A.1.28 (M) The ERMS must not, by its own architecture or design, impose any practical limit on the number of folders which can be created under any class, or within the entire ERMS.
Metadata standard Working group• Office of the e-Envoy• HM Customs and Excise• Department of Trade and Industry• Department for Transport, Local Government and the
Regions• Department of Health• Lord Chancellor’s Department• Ministry of Defence• National Archives of Scotland• National Assembly for Wales• Scottish Parliament• Cornwell Management Consultants plc
Records management elements• 1. Identifier• 2. Title• 3. Subject• 4. Description• 5. Creator• 6. Date• 7. Addressee• 8. Record type
• 9. Relation• 10. Aggregation• 11. Language• 12. Location• 13. Rights• 14. Disposal• 15. Digital signature*• 16. Preservation*• 17. Mandate
Reference Document (2007)
• GLOSSARY OF TERMS • DESCRIPTION OF ENTITIES • MAPPING OF FUNCTIONAL
REQUIREMENTS AND TERMINOLOGY
Implementation guidance (2004)
• Functionality supporting Freedom of Information implementation and other openness legislation
• Rôles and responsibilities (functional access rights)– Access control configuration issues
• Archival requirements– The implementation of a business classification
scheme should be of use in distinguishing important information from the ephemeral.
• XML schema representation of records management Metadata standard
Generic requirements for sustainingelectronic information over time:
1. Defining the characteristics for authentic records
• This document has been published as the first volume of a set of four which are provided to give central government departments an understanding of the principles which underpin any attestation that a record or a category of electronic records are considered to be authentic …
• The requirement for authenticity will mean that any software migration between formats will need to be managed and documented with care so that the reasons for the migration are explicit and the method used to validate the quality of the document following migration is clear. It should be emphasised that documentation of migration particularly needs to detail the methods used to effect the migration.
