This page (revision-50) was last changed on 12-May-2016 15:24 by Chris Martin

This page was created on 17-Sep-2012 14:49 by Alison Bennett

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
50 12-May-2016 15:24 16 KB Chris Martin to previous
49 11-May-2016 12:47 16 KB Chris Martin to previous | to last
48 21-Apr-2016 16:51 16 KB Stephanie Leith to previous | to last
47 28-Mar-2015 14:46 16 KB Suzy Blake to previous | to last
46 28-Mar-2015 14:44 16 KB Suzy Blake to previous | to last
45 28-Mar-2015 14:35 16 KB Suzy Blake to previous | to last
44 28-Mar-2015 14:32 16 KB Suzy Blake to previous | to last
43 27-Mar-2015 14:16 16 KB Suzy Blake to previous | to last
42 27-Mar-2015 14:15 16 KB Suzy Blake to previous | to last
41 27-Mar-2015 14:10 16 KB Suzy Blake to previous | to last

Page References

Incoming links Outgoing links
SectionB.5
SectionB.5

Version management

Difference between version and

At line 15 changed one line
During the 1990s much work was undertaken by the RCHME's Data Standards Unit (now part of English Heritage) in partnerships with English Heritage and ALGAO to develop the data model for recording SMR-type information. The event-monument-source data model began to be introduced in the early 1990s when it was adopted by the RCHME for its MONARCH database, by English Heritage in its data standard for urban archaeological databases and by Northamptonshire SMR and a few others. Throughout the 1990s there was considerable discussion about this data model led by Glenn Foard, Steve Catney, Neil Lang, Nigel Clubb and Steve Stead. The establishment of the Data Standards Working Party, now known as FISH (the Forum for Information Standards in Heritage), a group dedicated to developing data standards for monument inventories, can be seen as a direct result of the general climate of discussion and debate (see also [B.8|SectionB.8]).
During the 1990s much work was undertaken by the RCHME's Data Standards Unit (now part of [Historic England|Glossary#Historic England|target='_blank']) in partnerships with English Heritage and ALGAO to develop the data model for recording SMR-type information. The event-monument-source data model began to be introduced in the early 1990s when it was adopted by the RCHME for its MONARCH database, by English Heritage in its data standard for urban archaeological databases and by Northamptonshire SMR and a few others. Throughout the 1990s there was considerable discussion about this data model led by Glenn Foard, Steve Catney, Neil Lang, Nigel Clubb and Steve Stead. The establishment of the Data Standards Working Party, now known as FISH (the Forum for Information Standards in Heritage), a group dedicated to developing data standards for monument inventories, can be seen as a direct result of the general climate of discussion and debate (see also [B.8|SectionB.8]).
At line 17 changed one line
The modern generation of HER databases aims to comply with the MIDAS data standard published by the RCHME in 1998 ([Lee 1998|Bibliography#Lee 1998|target='_blank']). These databases enable information about monuments, events, sources and the management process to be recorded with equal weight. Nationally agreed reference datasets, such as the English Heritage Thesaurus of Monument Types and other lists published in INSCRIPTION, are incorporated into the databases (see also [B.7.3|http://archaeologydataservice.ac.uk/ifp/Wiki.jsp?page=SectionB.7#section-SectionB.7-B.7.3MIDASAndINSCRIPTION]). Features of the systems, such as pull-down lists and validated entry to key index fields, help to ease the adoption of data standards and promote consistency between HER systems. In general professional applications developers have produced these systems and, as a result, they incorporate features such as data-input forms, standard queries and reports that ease their day-to-day use by HER officers.
The modern generation of HER databases aims to comply with the MIDAS data standard published by the RCHME in 1998 ([Lee 1998|Bibliography#Lee 1998|target='_blank']). These databases enable information about monuments, events, sources and the management process to be recorded with equal weight. Nationally agreed reference datasets, such as the [Historic England|Glossary#Historic England|target='_blank'] Thesaurus of Monument Types and other lists published in INSCRIPTION, are incorporated into the databases (see also [B.7.3|http://archaeologydataservice.ac.uk/ifp/Wiki.jsp?page=SectionB.7#section-SectionB.7-B.7.3MIDASAndINSCRIPTION]). Features of the systems, such as pull-down lists and validated entry to key index fields, help to ease the adoption of data standards and promote consistency between HER systems. In general professional applications developers have produced these systems and, as a result, they incorporate features such as data-input forms, standard queries and reports that ease their day-to-day use by HER officers.
At line 21 changed one line
In 2004 the four Welsh Archaeological Trusts, who curate the four Welsh Regional Historic Environment Records, embarked on a collaborative venture to produce a bespoke, web based database system, running in MySQL and having an integrated web GIS, to accommodate all four HERs. Since then the system has continued to develop and is now called HEROS (Historic Environment Record Open System.
In 2004 the four Welsh Archaeological Trusts, who curate the four Welsh Regional Historic Environment Records, embarked on a collaborative venture to produce a bespoke, web based database system, running in MySQL and having an integrated web GIS, to accommodate all four HERs. Since then the system has continued to develop and is now called HEROS (Historic Environment Record Open System).
At line 23 changed one line
A decision may also need to be made as to which database platform to use. Some HERs use web-based platforms, such as Oxford ArchDigital’s TOAD system. Many HER databases use software applications such as Microsoft Access or other database packages designed primarily for desktop use, such as exeGesIS’s HBSMR software. Where the database is networked to allow multiple access to shared files for users, the host organisation’s IT support can be distrustful of the stability of software programs such as these, and be reluctant to provide support. Their concerns centre on issues of performance, robustness, backup management and security. HER managers may find themselves pressurised to move to a server-based relational database management system (RDBMS) such as SQL Server or Oracle. Generally speaking, server-based RDBMSs will suit very large databases with a high number of concurrent users, as they also have better stability, performance, security and backup procedures. However desktop applications are generally easier to use, give the HER manager more control over the database and have a cheaper license cost, suiting smaller databases with fewer concurrent users. exeGesIS SDM Ltd has developed a SQL Server backed version of their HBSMR software.
A decision may also need to be made as to which database platform to use, some HERs may choose to use web-based platforms. Many HER databases use software applications such as Microsoft Access or other database packages designed primarily for desktop use, such as exeGesIS’s HBSMR software. Where the database is networked to allow multiple access to shared files for users, the host organisation’s IT support can be distrustful of the stability of software programs such as these, and be reluctant to provide support. Their concerns centre on issues of performance, robustness, backup management and security. HER managers may find themselves pressurised to move to a server-based relational database management system (RDBMS) such as SQL Server or Oracle. Generally speaking, server-based RDBMSs will suit very large databases with a high number of concurrent users, as they also have better stability, performance, security and backup procedures. However desktop applications are generally easier to use, give the HER manager more control over the database and have a cheaper license cost, suiting smaller databases with fewer concurrent users. exeGesIS SDM Ltd has developed a SQL Server backed version of their HBSMR software.
This page (revision-50) was last changed on 12-May-2016 15:24 by Chris MartinTop