subject:"\[Archivesspace_Users_Group\] how to encode open\-ended date ranges\?"

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Edgar Garcia

I'd like to add, as someone previously on the Dev-Pri group, if you have 
interest in the feature that Benn pointed to which he submitted, clicking on 
Watch, and Voting for the ticket (available after logging into Jira near the 
upper right portion) will greatly help in getting this ticket completed.

I can see that the ticket was already passed into ready for implementation back 
in February and is waiting to be picked up but with more activity, a developer 
might pick it up faster.

Regards,
Edgar


Edgar Garcia

Senior Software Developer

IT Infrastructure

Northwestern University Libraries

Evanston, IL


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Benn 
Joseph 
Sent: Thursday, October 13, 2022 1:09 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?


We’re largely trying to avoid using date expressions too, for the same 
reasons—and this 
ticket<https://urldefense.com/v3/__https://archivesspace.atlassian.net/browse/ANW-1273__;!!Dq0X2DkFhyF93HkjWTBQKhk!WYkOLHT2VKrv8grDaKj41Y0CRoQkRla7LnwKYEaQrJ8HBuB81B7cQ6wDh-poRPhf5N4BaPuSh-AR6akjNgcdy1tTqFfJxjCgj2UlWp4$>
 is something we’re hoping will be approved at some point to make the 
normalized dates a little easier to read for users.

--Benn



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Ron Van 
den Branden
Sent: Thursday, October 13, 2022 11:02 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?



Hi Jim,



Thanks for your thoughts. We’re aiming at minimizing the use of date 
expressions as much as possible, in order to:

  *   Reduce the workload and avoid the need to record date information twice 
(once as date expression, once as standardized date)
  *   Reduce the amount of possible input error and ambiguity caused by that 
redundancy

In other words: if registrants have to enter a date, it would seem most 
efficient if they could express this as just a standardized date, which is both 
precise and machine-processable. Also, for exchangeability, a precise 
standardized representation of dates would seem preferable over date 
expressions, wouldn’t it?



Best,



Ron



Van: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 Namens James E. Cross
Verzonden: donderdag 13 oktober 2022 16:56
Aan: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?



Another thought: use single date in both cases and let the “Date Expression” 
field indicate that it is open-ended, i.e. single date “1990,” date expression 
“1990 - ” or single date “1990,” date expression “1990 (end date)” The date 
expression is what the user will see in the PUI.



Jim





James Cross
Manuscripts Archivist
Special Collections and Archives
Clemson University

Strom Thurmond Institute Building

230 Kappa Street

Clemson, SC  29634

jcr...@clemson.edu<mailto:jcr...@clemson.edu>

864.656.5182
http://library.clemson.edu/specialcollections/<https://urldefense.com/v3/__http:/library.clemson.edu/specialcollections/__;!!Dq0X2DkFhyF93HkjWTBQKhk!Vhv7kTVtnT65Ea6wvRVHjpJxPAGILvbvp5uxHvgQMY1hz876NvjNUT1ud7NpUoLSyhAbV7lvXsqNxGnMEAdcYXey5ZmTmr7OpUUB0Iiz$>



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?



Hi,



We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known

…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.



Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.com/v3/__https:/www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUry3C2sr$>),
 I’ll outline the observations and option

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Benn Joseph

We’re largely trying to avoid using date expressions too, for the same 
reasons—and this ticket<https://archivesspace.atlassian.net/browse/ANW-1273> is 
something we’re hoping will be approved at some point to make the normalized 
dates a little easier to read for users.
--Benn

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Ron Van 
den Branden
Sent: Thursday, October 13, 2022 11:02 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi Jim,

Thanks for your thoughts. We’re aiming at minimizing the use of date 
expressions as much as possible, in order to:

  *   Reduce the workload and avoid the need to record date information twice 
(once as date expression, once as standardized date)
  *   Reduce the amount of possible input error and ambiguity caused by that 
redundancy
In other words: if registrants have to enter a date, it would seem most 
efficient if they could express this as just a standardized date, which is both 
precise and machine-processable. Also, for exchangeability, a precise 
standardized representation of dates would seem preferable over date 
expressions, wouldn’t it?

Best,

Ron

Van: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 Namens James E. Cross
Verzonden: donderdag 13 oktober 2022 16:56
Aan: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Another thought: use single date in both cases and let the “Date Expression” 
field indicate that it is open-ended, i.e. single date “1990,” date expression 
“1990 - ” or single date “1990,” date expression “1990 (end date)” The date 
expression is what the user will see in the PUI.

Jim


James Cross
Manuscripts Archivist
Special Collections and Archives
Clemson University

Strom Thurmond Institute Building
230 Kappa Street
Clemson, SC  29634
jcr...@clemson.edu<mailto:jcr...@clemson.edu>
864.656.5182
http://library.clemson.edu/specialcollections/<https://urldefense.com/v3/__http:/library.clemson.edu/specialcollections/__;!!Dq0X2DkFhyF93HkjWTBQKhk!Vhv7kTVtnT65Ea6wvRVHjpJxPAGILvbvp5uxHvgQMY1hz876NvjNUT1ud7NpUoLSyhAbV7lvXsqNxGnMEAdcYXey5ZmTmr7OpUUB0Iiz$>

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.com/v3/__https:/www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUry3C2sr$>),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Dan Michelson

Hi All,

Just as a quick addition to this conversation, there is an approved ticket
<https://archivesspace.atlassian.net/browse/ANW-1475> pending development
that would (in my biased opinion) greatly improve how date records are
structured and created in ArchivesSpace.

If this were implemented right now, you could simply import the records as
inclusive dates with a date begin of 1969 and a date end of 2022 (with
certainty set to "not after" on the end date).

All the best,

Dan

On Thu, Oct 13, 2022 at 12:14 PM Clair, Kevin  wrote:

> Hi Ron,
>
> ArchivesSpace doesn't require that both Begin and End fields are populated
> when the date type is Inclusive. We have a handful of dates in our database
> with an expression of "after" or "post" a particular year, where we've set
> the Begin to that year and left the End null. As far as indexing is
> concerned it gets us where we'd like to be.
>
> (Whether the ways we've done this in the past is DACS-compliant is a
> discussion for another time.)  -k
> --
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Ron
> Van den Branden 
> *Sent:* Thursday, October 13, 2022 11:52 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] how to encode open-ended date
> ranges?
>
>
> Hi Kate,
>
>
>
> I realize my analysis might have been biased by a data-oriented view on
> our current data, which contains quite a number of archival objects with
> only a start date, and some with only an end date. I’ve asked my
> colleagues, and open-ended dates are indeed uncommon for resources,
> accessions, archival, or digital objects: they’ll be mostly ranges with a
> known start and end date.
>
>
>
> How to interpret these single dates in our data is probably a matter of
> internal interpretation on our end, but still: what is the
> intended/preferred notation in ArchivesSpace? If the creation time span for
> a subseries is determined as e.g. 1969, how should this be encoded:
>
>- Single date
>   - Begin date = 1969
>- Inclusive date
>   - Begin date = 1969
>   - End date = 1969
>
> ?
>
>
>
> Best,
>
>
>
> Ron
>
>
>
> *Van:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *Namens *Bowers,
> Kate A.
> *Verzonden:* donderdag 13 oktober 2022 16:57
> *Aan:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Onderwerp:* Re: [Archivesspace_Users_Group] how to encode open-ended
> date ranges?
>
>
>
> Can you explain the case for open-ended dates for resources, accessions,
> archival, or digital objects?
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Ron
> Van den Branden
> *Sent:* Thursday, October 13, 2022 10:32 AM
> *To:* archivesspace_users_group@lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] how to encode open-ended date
> ranges?
>
>
>
> Hi,
>
>
>
> We’re in the process of migrating data to ArchivesSpace, and one thing I’m
> still struggling with is how to encode open-ended date ranges, using
> standardized dates only. In other words: how to express:
>
>- the fact that only a start date is known
>- or the fact that only an end date is known
>
> …while still indicating this known date is the start / end of a range
> whose other end is not known; as opposite to expressing a precise
> singular/punctual date.
>
>
>
> Given the fact that ArchivesSpace currently uses 2 distinct date models
> for accessions, resources/archival objects and digital objects vs agents
> (see
> https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3DcH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8%26e%3D=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=m7TjWVJkrdOrGrS5Fuz8nkD067qwgpZ4IJlE9tEa%2Bxk%3D=0>),
> I’ll

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Clair, Kevin

Hi Ron,

ArchivesSpace doesn't require that both Begin and End fields are populated when 
the date type is Inclusive. We have a handful of dates in our database with an 
expression of "after" or "post" a particular year, where we've set the Begin to 
that year and left the End null. As far as indexing is concerned it gets us 
where we'd like to be.

(Whether the ways we've done this in the past is DACS-compliant is a discussion 
for another time.)  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Ron Van 
den Branden 
Sent: Thursday, October 13, 2022 11:52 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?


Hi Kate,



I realize my analysis might have been biased by a data-oriented view on our 
current data, which contains quite a number of archival objects with only a 
start date, and some with only an end date. I’ve asked my colleagues, and 
open-ended dates are indeed uncommon for resources, accessions, archival, or 
digital objects: they’ll be mostly ranges with a known start and end date.



How to interpret these single dates in our data is probably a matter of 
internal interpretation on our end, but still: what is the intended/preferred 
notation in ArchivesSpace? If the creation time span for a subseries is 
determined as e.g. 1969, how should this be encoded:

  *   Single date
 *   Begin date = 1969
  *   Inclusive date
 *   Begin date = 1969
 *   End date = 1969

?



Best,



Ron



Van: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 Namens Bowers, Kate A.
Verzonden: donderdag 13 oktober 2022 16:57
Aan: Archivesspace Users Group 
Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?



Can you explain the case for open-ended dates for resources, accessions, 
archival, or digital objects?



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?



Hi,



We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known

…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.



Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html%26d%3DDwMGaQ%26c%3DWO-RGvefibhHBZq3fL85hQ%26r%3Dwwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY%26m%3DhwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz%26s%3DcH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8%26e%3D=05%7C01%7Ckmc35%40psu.edu%7C41415742bb1344a9c63b08daad32e962%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638012731654163667%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=m7TjWVJkrdOrGrS5Fuz8nkD067qwgpZ4IJlE9tEa%2Bxk%3D=0>),
 I’ll outline the observations and options I’m seeing.



[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required

Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date

?

This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?



[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory

Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Ron Van den Branden

Hi Jim,

Thanks for your thoughts. We’re aiming at minimizing the use of date 
expressions as much as possible, in order to:

  *   Reduce the workload and avoid the need to record date information twice 
(once as date expression, once as standardized date)
  *   Reduce the amount of possible input error and ambiguity caused by that 
redundancy
In other words: if registrants have to enter a date, it would seem most 
efficient if they could express this as just a standardized date, which is both 
precise and machine-processable. Also, for exchangeability, a precise 
standardized representation of dates would seem preferable over date 
expressions, wouldn’t it?

Best,

Ron

Van: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 Namens James E. Cross
Verzonden: donderdag 13 oktober 2022 16:56
Aan: Archivesspace Users Group 
Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Another thought: use single date in both cases and let the “Date Expression” 
field indicate that it is open-ended, i.e. single date “1990,” date expression 
“1990 - ” or single date “1990,” date expression “1990 (end date)” The date 
expression is what the user will see in the PUI.

Jim


James Cross
Manuscripts Archivist
Special Collections and Archives
Clemson University

Strom Thurmond Institute Building
230 Kappa Street
Clemson, SC  29634
jcr...@clemson.edu<mailto:jcr...@clemson.edu>
864.656.5182
http://library.clemson.edu/specialcollections/

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.com/v3/__https:/www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUry3C2sr$>),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note: in EAC output, the begin/end qualification is dismissed: both are 
exported without distinction as e.g.
2022-10-08

  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively

  *   open-ended date range: ?
==> problem if only end date is known, since begin date is mandatory
In other words: how would one differentiate between, e.g.:

  *   birth date of a living person (1990 - )
  *   birth date of a deceased person, whose death date is unknown (1800 - ?)
  *   death date of a person whose birth date is unknown (? - 1950)
?

The documentation in the ArchivesSpace Help Center merely documents the 
different fields, but I couldn’t find much guidance on how to use them in 
practice. The DACS, EAD, and EAC documentation is rather sparse as well 
regarding open-ended date ranges. Therefore, any guidance on this matter would 
be much appreciated!

Best,

Ron

Ron Van den Branden | function

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Ron Van den Branden

Hi Kate,

I realize my analysis might have been biased by a data-oriented view on our 
current data, which contains quite a number of archival objects with only a 
start date, and some with only an end date. I’ve asked my colleagues, and 
open-ended dates are indeed uncommon for resources, accessions, archival, or 
digital objects: they’ll be mostly ranges with a known start and end date.

How to interpret these single dates in our data is probably a matter of 
internal interpretation on our end, but still: what is the intended/preferred 
notation in ArchivesSpace? If the creation time span for a subseries is 
determined as e.g. 1969, how should this be encoded:

  *   Single date
 *   Begin date = 1969
  *   Inclusive date
 *   Begin date = 1969
 *   End date = 1969
?

Best,

Ron

Van: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 Namens Bowers, Kate A.
Verzonden: donderdag 13 oktober 2022 16:57
Aan: Archivesspace Users Group 
Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Can you explain the case for open-ended dates for resources, accessions, 
archival, or digital objects?

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Ron Van den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz=cH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8=>),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note: in EAC output, the begin/end qualification is dismissed: both are 
exported without distinction as e.g.
2022-10-08

  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively

  *   open-ended date range: ?
==> problem if only end date is known, since begin date is mandatory
In other words: how would one differentiate between, e.g.:

  *   birth date of a living person (1990 - )
  *   birth date of a deceased person, whose death date is unknown (1800 - ?)
  *   death date of a person whose birth date is unknown (? - 1950)
?

The documentation in the ArchivesSpace Help Center merely documents the 
different fields, but I couldn’t find much guidance on how to use them in 
practice. The DACS, EAD, and EAC documentation is rather sparse as well 
regarding open-ended date ranges. Therefore, any guidance on this matter would 
be much appreciated!

Best,

Ron

Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Musea en Erfgoed
Minderbroedersstraat 22, 2000 Antwerpen
✉ Grote Markt 1, 2000 Antwerpen
gsm +32 0485 02 80 50 | tel. +32 3 222

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Bowers, Kate A.

Can you explain the case for open-ended dates for resources, accessions, 
archival, or digital objects?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Ron Van 
den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mail-2Darchive.com_archivesspace-5Fusers-5Fgroup-40lyralists.lyrasis.org_msg05341.html=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz=cH9UvNvbKkbEcG88o6pqGcf3-0l_7L5sIV0c3bplsR8=>),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note: in EAC output, the begin/end qualification is dismissed: both are 
exported without distinction as e.g.
2022-10-08

  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively

  *   open-ended date range: ?
==> problem if only end date is known, since begin date is mandatory
In other words: how would one differentiate between, e.g.:

  *   birth date of a living person (1990 - )
  *   birth date of a deceased person, whose death date is unknown (1800 - ?)
  *   death date of a person whose birth date is unknown (? - 1950)
?

The documentation in the ArchivesSpace Help Center merely documents the 
different fields, but I couldn’t find much guidance on how to use them in 
practice. The DACS, EAD, and EAC documentation is rather sparse as well 
regarding open-ended date ranges. Therefore, any guidance on this matter would 
be much appreciated!

Best,

Ron

Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Musea en Erfgoed
Minderbroedersstraat 22, 2000 Antwerpen
✉ Grote Markt 1, 2000 Antwerpen
gsm +32 0485 02 80 50 | tel. +32 3 222 93 30
letterenhuis.be<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.letterenhuis.be_=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz=RCdANiyeGbpOaHKErHK7dN3hVi4Xjiqw7EG9JmMGEIM=>
 | 
instagram<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.instagram.com_letterenhuis_=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz=23CBQ1OTniE_zIpk904UheXNdpIsl_Gs62ZkcZgRQN4=>
 | 
facebook<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_Letterenhuis=DwMGaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hwhUWCl8DmiVBAr8KCWWuvqIpF5qGU38NpEyKdpmIIC_b1sDZ08xKIYeni9Jn1Sz=Vas9PGIxYEolJnQuVo9qEE1hue_eztFb4vZEFEOLCUE=>

Proclaimer
Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet 
voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. 
Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad 
Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als 
stad nemen we privacy heel serieus en willen we als een goe

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread James E. Cross

Another thought: use single date in both cases and let the “Date Expression” 
field indicate that it is open-ended, i.e. single date “1990,” date expression 
“1990 - ” or single date “1990,” date expression “1990 (end date)” The date 
expression is what the user will see in the PUI.

Jim


James Cross
Manuscripts Archivist
Special Collections and Archives
Clemson University

Strom Thurmond Institute Building
230 Kappa Street
Clemson, SC  29634
jcr...@clemson.edu<mailto:jcr...@clemson.edu>
864.656.5182
http://library.clemson.edu/specialcollections/


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Ron Van 
den Branden
Sent: Thursday, October 13, 2022 10:32 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html<https://urldefense.com/v3/__https:/www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUry3C2sr$>),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note: in EAC output, the begin/end qualification is dismissed: both are 
exported without distinction as e.g.
2022-10-08

  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively

  *   open-ended date range: ?
==> problem if only end date is known, since begin date is mandatory
In other words: how would one differentiate between, e.g.:

  *   birth date of a living person (1990 - )
  *   birth date of a deceased person, whose death date is unknown (1800 - ?)
  *   death date of a person whose birth date is unknown (? - 1950)
?

The documentation in the ArchivesSpace Help Center merely documents the 
different fields, but I couldn’t find much guidance on how to use them in 
practice. The DACS, EAD, and EAC documentation is rather sparse as well 
regarding open-ended date ranges. Therefore, any guidance on this matter would 
be much appreciated!

Best,

Ron

Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Musea en Erfgoed
Minderbroedersstraat 22, 2000 Antwerpen
✉ Grote Markt 1, 2000 Antwerpen
gsm +32 0485 02 80 50 | tel. +32 3 222 93 30
letterenhuis.be<https://urldefense.com/v3/__http:/www.letterenhuis.be/__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUtO9V0vc$>
 | 
instagram<https://urldefense.com/v3/__https:/www.instagram.com/letterenhuis/__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUorJZpFU$>
 | 
facebook<https://urldefense.com/v3/__https:/www.facebook.com/Letterenhuis__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUsUvzyqI$>

Proclaimer
Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet 
voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. 
Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad 
Antwerpen. Ze kunnen vertrouwelijke of persoonlijke inform

[Archivesspace_Users_Group] how to encode open-ended date ranges?

2022-10-13 Thread Ron Van den Branden

Hi,

We’re in the process of migrating data to ArchivesSpace, and one thing I’m 
still struggling with is how to encode open-ended date ranges, using 
standardized dates only. In other words: how to express:

  *   the fact that only a start date is known
  *   or the fact that only an end date is known
…while still indicating this known date is the start / end of a range whose 
other end is not known; as opposite to expressing a precise singular/punctual 
date.

Given the fact that ArchivesSpace currently uses 2 distinct date models for 
accessions, resources/archival objects and digital objects vs agents (see 
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html),
 I’ll outline the observations and options I’m seeing.

[1] Accessions, resources, archival objects, digital objects:

  *   “Single” date only offers a single date field, labeled “Begin”
  *   “Inclusive” date offers both a “Begin” and “End” date field, only one of 
which is required
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as “Begin” date
  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively
  *   open-ended date range: “inclusive” date, with known date as either 
“Begin” or “End” date
?
This leads me to the question whether in practice “single” dates are used at 
all for anything except accession dates, creation dates of digital objects, or 
as dates for only the lowest-level archival objects?

[2] Agents:

  *   “Single” date only offers a single date field, which can be labeled as 
either “Begin” or “End”
  *   “Inclusive” date offers both a “Begin” and “End” date field, of which 
“Begin” is mandatory
Would this be a good strategy:

  *   “singular/punctual” dates: “single” date, one value as either “Begin” or 
“End” date

Note: in EAC output, the begin/end qualification is dismissed: both are 
exported without distinction as e.g.
2022-10-08

  *   date range: “inclusive” date, start and end dates as “Begin” and “End” 
dates, respectively

  *   open-ended date range: ?
==> problem if only end date is known, since begin date is mandatory
In other words: how would one differentiate between, e.g.:

  *   birth date of a living person (1990 - )
  *   birth date of a deceased person, whose death date is unknown (1800 - ?)
  *   death date of a person whose birth date is unknown (? - 1950)
?

The documentation in the ArchivesSpace Help Center merely documents the 
different fields, but I couldn’t find much guidance on how to use them in 
practice. The DACS, EAD, and EAC documentation is rather sparse as well 
regarding open-ended date ranges. Therefore, any guidance on this matter would 
be much appreciated!

Best,

Ron

Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Musea en Erfgoed
Minderbroedersstraat 22, 2000 Antwerpen
✉ Grote Markt 1, 2000 Antwerpen
gsm +32 0485 02 80 50 | tel. +32 3 222 93 30
letterenhuis.be | 
instagram | 
facebook

Proclaimer
Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet 
voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. 
Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad 
Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als 
stad nemen we privacy heel serieus en willen we als een goede huisvader waken 
over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt 
ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te 
verwijderen en het niet verder te verspreiden of te kopiëren.


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?

[Archivesspace_Users_Group] how to encode open-ended date ranges?

9 matches

Site Navigation

Mail list logo

Footer information