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

Help for MCG Archives


MCG Archives

MCG Archives


MCG@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

MCG Home

MCG Home

MCG  November 2013

MCG November 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Displaying imprecise date and location information - best practice and examples?

From:

Joseph Padfield <[log in to unmask]>

Reply-To:

Museums Computer Group <[log in to unmask]>

Date:

Thu, 7 Nov 2013 14:25:54 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (148 lines)

Hi Alec,

For "Early 3rd Century BC" I would have probably said "300BC - 275BC" 
with going all the way to 250 BC being the "First Half" or something 
similar. But I don't know if there really is a "correct" answer.

Joe

On 06/11/13 14:35, Alec Turner wrote:
> This is a subject close to my own heart as I wrote and maintain the 
> date translation software used within MuseumIndex+, etc. You're right 
> about variation in the meaning of circa, not just across different 
> systems, but when applied to different date spans (e.g. in 
> MuseumIndex+ it's default meaning, which can also be tweaked per 
> customer, can be different when applied to months, years, decades and 
> centuries). Ultimately we've always allowed access to the generated 
> "earliest" and "latest" date values so these can be adjusted manually 
> if the builtin rules get it wrong. I'd be curious to know what people 
> would ideally like their systems to do.
>
> Finally, I couldn't resist testing out your "Early 3rd Century BC" 
> example - MuseumIndex+ interprets this as "299 BC - 250 BC". Are we in 
> the right ballpark? (because I'd be happy to try and improve on this 
> if people think we're not).
>
> ... Alec Turner
>
> On 04/11/2013 14:03, Joseph Padfield wrote:
>> Hi,
>>
>> I had a little look at this a few years ago while experimenting with the
>> conversion of free text dates to semantic searchable dates. I was
>> working with the questions: Given the language used within the TMS
>> DisplayDate field; which paintings/artists do we want someone to find
>> when they run a date based search for a particular year or even a range
>> of years?
>>
>> I ended up using a lot of regular expressions in Perl to create an
>> internally consistent display text field and then used a set of simple
>> rules to indicate what date range the display date referred to. As I
>> said it was a few years ago for an in-house R&D project, but if it is
>> useful you can see some of the details at:
>> http://research.ng-london.org.uk/wiki/index.php/National_Gallery_Display_Date_Descriptors 
>>
>>
>>
>> These ranges where just an example and the actual date range used could
>> be different for different systems, ideally though you just need to add
>> the description of your logic into the "help" information.
>>
>> Joe
>>
>> PS the one I always like was what years are meant by: "Early 3rd Century
>> BC" :-)
>>
>> On 04/11/13 11:54, David Croft wrote:
>>> I've been working on this problem on an off for a while now, but from
>>> the other side as it were. Trying to extract the dates that the record
>>> author meant from what they actually wrote.
>>> There are a LOT of different date formats out there and I've yet to
>>> see a really good solution.
>>> I'm coming at this problem from a software angle, trying to decode
>>> dates automatically, so my desires for date formats may be different
>>> to yours.
>>> But I really, really, really wish that date information was stated
>>> explicitly and consistently.
>>>
>>> Plenty of collections use modifiers like 'circa', 'early' or 'first
>>> half', but then don't use these consistently.
>>> In one record 'late 20th century' means 1950 to 2000, in another place
>>> it will mean 1975 to 2000.
>>> These sort of date modifiers never seem to get explicitly defined for
>>> the collection which means that what one collection means by 'circa'
>>> is different to what another collection means.
>>> The modifiers also mean different things to different dates, 'circa
>>> 1950' may mean 1945 to 1955 but is `circa 1950s' 1950 to 1959 or 1945
>>> to 1965?
>>> There are lots of records with dates like '80s' where you just have to
>>> assume the century information or '1940-50s' where you assume it means
>>> 1940 to 1959.
>>>
>>> So for me, the best way is just to provide the upper and lower bounds
>>> for date period in full, i.e. not `circa 1955' but instead `1950/1/1
>>> to 1959/12/31`.
>>> Or if that's not possible, define exactly what you mean by 'circa',
>>> 'late', 'early' etc and make that information available where anyone
>>> looking at your records can see it.
>>> For example, are you going to use the word 'circa'? or just put a 'c'
>>> on the front of the date i.e. 'c1950'?
>>> If there are two dates in a field does the circa apply to just the
>>> first one or both? i.e. is 'circa 1950 to 1960' the same as 'circa
>>> 1950 to circa 1960'?
>>> If you are saying 'circa 19th century' do you mean up to 25 years
>>> either side? 50 years? 75?
>>> Software can decode any format you use as long as we know what the
>>> rules are.
>>>
>>> P.S
>>> There are some truly interesting date fields out there and I've been
>>> keeping a list as part of my really tricky testing data.
>>> Some of my favourites are '25 feb ?', 'circa pre world war two',
>>> 'early or late 19th or 20 century' and 'c18-1 to c--01?'
>>>
>>> David
>>>
>>> ****************************************************************
>>>         website:  http://museumscomputergroup.org.uk/
>>>         Twitter:  http://www.twitter.com/ukmcg
>>>        Facebook:  http://www.facebook.com/museumscomputergroup
>>>   [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>>> ****************************************************************
>>> .
>>>
>>
>
> .
>

-- 
*Joseph Padfield*
Conservation Scientist
Scientific Department
The National Gallery
Trafalgar Square
London WC2N 5DN
44 (0)20 7747 2553
http://research.ng-london.org.uk
http://www.twitter.com/JoePadfield


----------------------------------------------------------------
Facing the Modern: The Portrait in Vienna 1900
9 October 2013 - 12 January 2014

Book now:
http://www.nationalgallery.org.uk/whats-on/exhibitions/vienna

Sign up for news, offers and exclusive competitions from the
National Gallery:
http://www.nationalgallery.org.uk/stay-in-touch

****************************************************************
       website:  http://museumscomputergroup.org.uk/
       Twitter:  http://www.twitter.com/ukmcg
      Facebook:  http://www.facebook.com/museumscomputergroup
 [un]subscribe:  http://museumscomputergroup.org.uk/email-list/
****************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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
2006
2005
2004
2003
2002
2001
2000
1999
1998


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