JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for HERFORUM Archives


HERFORUM Archives

HERFORUM Archives


HERFORUM@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

HERFORUM Home

HERFORUM Home

HERFORUM  June 2006

HERFORUM June 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Multiple Indexing

From:

joanne cook <[log in to unmask]>

Reply-To:

Issues related to Historic Environment Records <[log in to unmask]>

Date:

Tue, 13 Jun 2006 09:07:04 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (263 lines)

Hi,
 
I'm not an HER person, rather a commercial archaeologist who happens to use a fair amount of data provided by HERs in my work, so forgive me if my point is not based on the same familiarity with the subject as the rest of you! I just have a point to make about the slightly broader issue of using this data in GIS packages and for analysis.
 
I agree with Simon, that a quantity field outside of the free text summary is really useful, if not vital. There are a couple of reasons for this. Firstly, I normally have to strip out the free text field (usually of type "memo") from any database before I can use the data in a GIS because the GIS can't handle that sort of data type properly. Therefore, if important objective data like quantities are in that field they are either lost, or I have to spend a long time copying the information that I need into another field. Secondly, how can you use that sort of data in any kind of analysis if you don't have an idea of quantities in a seperate field? 
 
I agree partially with the argument that a quantity implies certainty, but surely you are recording only what has been found (which should be a certainty), rather than assuming that you know how many monuments/features/finds are actually there (which is a complete unknown)?
 
Thanks
 
Jo
 
-------------------------------------------
Joanne Cook BSc MLitt AIFA
Information Systems Coordinator
Oxford Archaeology North
-------------------------------------------

________________________________

From: Issues related to Historic Environment Records on behalf of Simon Walton
Sent: Mon 12/06/2006 15:58
To: [log in to unmask]
Subject: Re: Multiple Indexing



Hi,

This could run and run. Placing this information in text means it is unobtainable without
printing the full record. Taking pottery as an example I would wish to know whether 1 or
70 examples had been found to provide some quantitative measure on the record and
before looking further. i.e. do I have a chance find or something more substantial. It
could always be qualified with another field e.g. AT LEAST, NO MORE THAN,
EXACTLY.

On a broader sense we don't stop quantifying 'how many roman villas' have been
recorded just in case there might be out there. We have to always assume that
absence of evidence does not mean evidence of absence and use the data accordingly.

cheers


Date sent:              Mon, 12 Jun 2006 13:33:46 +0100
Send reply to:          Issues related to Historic Environment Records              <[log in to unmask]>
From:                   "CARLISLE, Phil" <[log in to unmask]>
Subject:                Re: Multiple Indexing
To:                     [log in to unmask]

> Hi Nick et al
> I think I'm right in saying that currently within AMIE the recording guidelines say not to use the quantity field but to note the quantity within both the summary and long text fields.
>
> I think the main reason for this is to do with the argument that was put forward, I think by Chris,
 that if you can't say for sure exactly how many burials may still be out there that it would be misleading to add a quantity.
>
> However just because the NMR doesn't use a quantity field, even though we have one, it doesn't mean that MIDAS2 shouldn't include the option.
>
> I think this is something that we as a community need to reach a consensus on and, as with other recommendations, apply as/when we see fit.
>
> This may be something which each HER should have a policy on. Whether it be one of inclusion or exclusion.
>
> I get the feeling this is going to run and run......
>
> Phil
>
>
>
> Phil Carlisle
> Data Standards Supervisor
> National Monuments Record Centre
> Kemble Drive
> Swindon
> SN2 2GZ
> +44 (0)1793 414824
> 
>
> The information contained within this e-mail is confidential and may be privileged. It is intended for the addressee only. If you have received the e-mail in error, please inform the sender and delete it from your system. The contents of this e-mail must not be disclosed to anyone else or copied without the sender's consent.
>
> Any views and opinions expressed in this message are those of the author and do not necessarily reflect those of English Heritage. English Heritage will not take any responsibility for the views of the author.
>
>
> -----Original Message-----
> From: Issues related to Historic Environment Records [mailto:[log in to unmask]] On Behalf Of Nick Boldrini
> Sent: 12 June 2006 09:02
> To: [log in to unmask]
> Subject: Re: Multiple Indexing
>
> Hi Phil
>
> sorry for any confusion I have caused!
>
> Can I just ask if this means there is an assumption at the moment that
> you don't index to quantity?
>
> Is this stated anywhere?
>
> I thought I had read it somewhere but could do with a reference, if
> anyone can think of one
>
> thanks
>
> best wishes
>
> Nick Boldrini
> Historic Environment Record Officer
> Heritage Section
> Countryside Service
> North Yorkshire County Council
> County Hall
> Northallerton
> DL7 8AH
> Direct Dial (01609) 532331
>
> Conserving North Yorkshire's heritage - encouraging sustainable access
> www.northyorks.gov.uk/archaeology
>
> This email is personal. It is not authorised by or sent on behalf of
> North Yorkshire
> County Council, however, the Council has the right and does inspect
> emails sent from
> and to its computer system. This email is the sole responsibility of
> the sender
>
> >>> [log in to unmask] 09/06/2006 09:19:02 >>>
> Hi everyone
> I'd just like to clear up any misunderstanding of what we mean by
> multiple indexing.
>
> I think all the issues have already been covered by both Tanja and
> Crispin but Simon has raised a pertinent point too ie that Monarch used
> to have a quantity field.
>
> This is indeed the case and the field is still retained, although much
> underused, in the current incarnation of the NMRs database AMIE.
>
> The issues relating to multiple indexing are the following.
>
> 1. If there is uncertainty as to what the monument is then both
> monument types should be indexed. Eg. if you have a mound in a field
> which could be a barrow or it could be a windmill mound, then you would
> double index (ie MULTIPLE INDEX) with both BARROW and WINDMILL MOUND.
>
> 2. If you have a monument type which is a non-preferred term which is
> represented in the thesaurus by two terms. Eg. Abbey Gate then you
> double index with ABBEY and GATE
>
> 3. If you have multiple monument types associated with one site eg. a
> BARROW CEMETERY which includes different BARROW types. In this instance
> you could just index as BARROW CEMETERY or you could multiple index
> with, BARROW CEMETERY, ROUND BARROW, DISC BARROW, BOWL BARROW etc.
>
> 4. If you have multiple occurrences of the same Monument Type eg.
> Chris's example of 1300 Inhumations then you (could) double index the
> record with INHUMATION CEMETERY and INHUMATION.
>
> Our suggestion is that we create a MIDAS unit of information called
> EXTENT.
>
> This would apply to monuments in the same way that ARCHIVE EXTENT is
> used.
>
> ARCHIVE EXTENT allows you to say how many items you have in a
> collection. So, for example, you can say in the BEDFORD LEMERE
> collection there are 52 boxes of photos. This means you don't have to
> create individual records for each box as all you are doing is
> signposting the size of the collection.
>
> Thus, Chris's example would appear as something like:
>
> PERIOD                MONUMENT TYPE           EXTENT/QUANTITY
> ANGLO-SAXON           INHUMATION CEMETERY     1
> ANGLO-SAXON           INHUMATION                      1300
>
> This would allow anyone searching for large inhumation cemeteries with
> high numbers of burials.
>
> For the most part the EXTENT/QUANTITY field could default to 1 with the
> ability to overwrite if/when necessary.
>
> We've only just started thinking about whether this should be included
> and welcome input from the HER community. Any thoughts on whether you
> think the addition of this unit of information would be useful, or not,
> would be greatly appreciated.
>
> I hope I've managed to assuage any fears people had about having to
> reindex millions of records.
>
> Phil
>
> Phil Carlisle
> Data Standards Supervisor
> National Monuments Record Centre
> Kemble Drive
> Swindon
> SN2 2GZ
> +44 (0)1793 414824
> 
>
> The information contained within this e-mail is confidential and may be
> privileged. It is intended for the addressee only. If you have received
> the e-mail in error, please inform the sender and delete it from your
> system. The contents of this e-mail must not be disclosed to anyone else
> or copied without the sender's consent.
>
> Any views and opinions expressed in this message are those of the
> author and do not necessarily reflect those of English Heritage. English
> Heritage will not take any responsibility for the views of the author.
>
>
> -----Original Message-----
> From: Issues related to Historic Environment Records
> [mailto:[log in to unmask]] On Behalf Of Nicholson, Andrew
> Sent: 08 June 2006 16:34
> To: [log in to unmask]
> Subject: Re: Multiple Indexing
>
> > When you revisit this, bear in mind what is reasonable.
> > 1300 inhumations were recently excavated from a single site
> > in the city. This is recorded as a inhimation cemtery.  I
> > refuse to create additional 1300 records!
> >
>
> Likewise for 132 small cairns in a cairnfield.
>
> Andy
>
> Andrew Nicholson
> SMR Officer
> Planning and Environment (Archaeology)
> Dumfries and Galloway Council
> Tel: 01387 260154   
> Fax: 01387 260149
> mailto:[log in to unmask]
> http://www.dumgal.gov.uk
>
> Any email message sent or received by the Council may require to be
> disclosed by the Council under the provisions of the Freedom of
> Information
> (Scotland) Act 2002.
>
>
> 
>
> WARNING
>
> This E-mail and any attachments may contain information that is confidential or privileged, and is intended solely for the use of the named recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or any action taken is prohibited and may be unlawful.
>
> Any opinions expressed are those of the author and not necessarily the view of the Council.
>
> North Yorkshire County Council.

Simon Walton
Systems Architect,
Project Jupiter, ext 3316







This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager