This page (revision-44) was last changed on 18-Sep-2012 10:40 by Alison Bennett

This page was created on 14-Jun-2012 11:29 by Alison Tinniswood

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
44 18-Sep-2012 10:40 1 KB Alison Bennett to previous
43 18-Sep-2012 10:37 1 KB Alison Bennett to previous | to last
42 14-Sep-2012 15:23 1 KB Alison Bennett to previous | to last
41 14-Sep-2012 15:11 46 KB Alison Bennett to previous | to last

Page References

Incoming links Outgoing links
SectionD...nobody
SectionD

Version management

Difference between version and

At line 261 changed one line
The ADS can offer advice on digital data transfers ([[email protected]|mailto:[email protected]]). The NMRE offer guidance on the use of the OASIS form ([email protected] ).
The ADS can offer advice on digital data transfers ([[email protected]|mailto:[email protected]]). The NMRE offer guidance on the use of the OASIS form ([[email protected]|mailto:[email protected]]).
At line 263 removed 2 lines
At line 264 added 5 lines
*confirming that the data is being supplied in accordance with core HER data standards
*checking that the data supplied has not been corrupted during transfer and is readable
*checking for spelling or data-input errors
*checking the data supplied against the written reports
*adding additional indexing information and other details.
At line 267 changed one line
· confirming that the data is being supplied in accordance with core HER data standards
While such forms are being introduced HER officers may need to allow time to work with both planning archaeologists and contractors to make sure that information is flowing efficiently from data collector to the HER.
At line 269 changed one line
· checking that the data supplied has not been corrupted during transfer and is readable
For Scotland see section above (D.3.4) re ASPIRE
At line 271 changed one line
· checking for spelling or data-input errors
!!D.4.3 Importing digital data from external sources
!Strategies for physically moving data between geographically removed locations
Various forms of electronic storage media are used to move data around. An important consideration is that both sender and receiver need to use a shared technology for successful data transfer:
*Tape has now been largely superseded as a transfer medium, mainly because few systems contain Digital Audio Tape (DAT) machines today.
*Standard 3.5 inch floppy disks can be used to transfer small amounts of data (1.44mb).
*Compression software can be used to produce zip files (for PCs) and tar files (for Unix systems) which increase the capacity of floppy discs. See [http://www.pkware.com|http://www.pkware.com] for information about PKZIP.
*CD ROMs and DVDs can transfer up to 650mb of data for CDs and 4.7 Gb for DVDs and are becoming commonplace as CD and DVD writers become more widespread. See [http://cd-info.com|http://cd-info.com] for information about CDs and DVDs.
*High-capacity floppy and Zip drives may also be used. For information see [http://www.winzip.com/winzip.html|http://www.winzip.com/winzip.html].
*Files may be transferred between users as attachments to email messages. File transfer is not without its problems as many mail servers refuse files over a certain size and 'bounce' messages back to the sender. There are also security implications as e-mall attachments are notoriously vulnerable to viruses.
*File Transfer Protocol (FTP) is an efficient way of transferring data but requires technical support. FTP is a communications program used to link source and destination systems, in which either the sender or receiver logs on to a remote system to effect a transfer. Security issues mean that many system administrators restrict access from outside although they may set up an area where files can be placed for transfer. For information about FTP see [http://www.ftpplanet.com/ftpresources/basics.htm|http://www.ftpplanet.com/ftpresources/basics.htm]
At line 273 changed one line
· checking the data supplied against the written reports
!Strategies for importing data into existing databases
Where the data is to be imported into an existing dataset there are a number of concordance issues:
*The new data need to be in a format acceptable for import to the software maintaining the existing database. ASCII delimited text is a standard export format for transfer into databases. In this format, a delimiting character separates the contents of the fields in a database record, for example a comma, percent or hash. Care must be taken to select a delimiter that is not present in the data. Most database applications support a number of import and export formats to facilitate the transfer of data between packages: for example as well as delimited text, Microsoft Access also supports import of data from other Access databases, Excel, Lotus, Paradox, Foxpro, dbase, Btrieve and SQL.
*There needs to be a clear mapping between the new data and the fields that define the structure of the existing database. Where possible, the HER should specify the fields for data capture.
*The new data should conform to any vocabulary control or data standards that have been agreed for the main database. Vocabulary lists should be supplied with the new data, particularly where codes are used. Candidate terms identified in the new data may need to be put forward for addition to existing wordlists or thesauri.
*The new data needs to be validated and may need to be edited or manipulated to conform with agreed core-data standards for the HER using search and replace functions.
At line 275 changed one line
· adding additional indexing information and other details.
Much of this can be achieved through the use of FISH Tools MIDAS Schema (see Section B 6, 7 for details). The Forum for Information Standards in Heritage (FISH) has undertaken a project to develop a toolkit of formats schema and protocols for data held in historic environment information resources (HEIRs).
At line 277 changed one line
These tools will help with:
*The provision of digital data from one organisation to another,
*The provision of data to the public,
*The archiving of digital data,
*The migration of data to new systems,
*Conformance to national standards.
At line 279 changed one line
While such forms are being introduced HER officers may need to allow time to work with both planning archaeologists and contractors to make sure that information is flowing efficiently from data collector to the HER.
The 'FISH interoperability toolkit' development project will provide the heritage data community with an essential infrastructure of shared standards. It has the potential to improve access to information for all.
At line 281 changed one line
__Useful Websites__:
FISH: [www.fish-forum|www.fish-forum]
At line 283 changed one line
For Scotland see section above (D.3.4) re ASPIRE
FISH Interoperabilty Toolkit [www.heritage-standards.org|www.heritage-standards.org]
This page (revision-44) was last changed on 18-Sep-2012 10:40 by Alison BennettTop