Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Vincent Meijer]

I second that, awesome to hear that this is in scope for the near future!

Thanks Alexei,

Vincent


On Jul 22, 2017 4:32 AM, "Joel Aldor"  wrote:

Hi Alexei,

This is something we're really looking forward to. Thanks a lot!

Regards,

Joel


On Saturday, July 22, 2017 at 2:18:20 AM UTC+8, Alexei Peters wrote:

> Hi Vincent,
> Here's the status of dates and the collection of date information in v4.
> As it stands v4.0.0 will only be able to collect date information in the
> few specific formats that you mention above: -MM-DD, -MM and 
> If you only want to collect  then you need to remember to set the
> format in the Card Designer (see attached screen shot).  I've verified that
> this will not add -01-01 to the date saved.
> As for the backend validation, we will try to sync that up before the
> release of v4.
>
> In the very near future(next couple of months) we will be addressing the
> "fuzzy date" issue so that users can collect anything that relates to a
> point or range of time and that won't force users to enter specific
> formats.  Eg: you could just specify the string  '*late third century
> B.C.*'
> Allowing something like this to participate in search will be the real
> trick, but I think it's at least partially achievable!
>
> Hope this helps.
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
> <(971)%20227-3173>
>
> On Tue, Jul 18, 2017 at 4:14 AM, Vincent Meijer 
> wrote:
>
>> Hi Alexei,
>>
>> What is the current status of fuzzy dates in Arches 4?
>>
>> I have been looking at the Arches code, and it seems the frontend
>> DatePicker only allows -MM-DD, -MM and  (*but no B.C.*).
>> However, in practice the datepicker automatically adds 01-01 when I only
>> enter a year.
>> The backend seems to have it's own date validation: 
>> '-%Y','%Y','%Y-%m-%d','%B-%m-%d','%Y-%m-%d
>> %H:%M:%S'
>>
>> I think being able to specify years only and B.C. years would be a good
>> start for our use case, but this would require that our users translate 
>> '*late
>> third century B.C.*' to something like '*-210*'. Seems sketchy.
>>
>> However, I just started thinking about this and maybe there are better
>> solutions. Thoughts welcome!
>>
>> Thanks!
>> Vincent
>>
>>
>> On Tuesday, 17 May 2016 17:57:30 UTC+2, Angela Labrador wrote:
>>
>>> Good thought, Adam - thanks for the feedback -- and great news that
>>> native support for a broader range of date types will be in version 4!
>>>
>>> On Wednesday, May 11, 2016 at 7:28:09 PM UTC-4, Adam Cox wrote:

 Hi Angela, this looks good and I appreciate the detailed documentation
 on how to install the extension.

 One thought I had is that you could move your validation into a new
 dedicated file, and then leave branch-list.js alone.  I did this in my
 current project, in order to create a centralized location for validation
 functions so I could apply them in any form. I created validation.js
 ,
 and then used it in each form like this
 
 (see lines 5, 9, and 80).  I have two basic functions in there now, but
 have thought that a simple nodeIsDigit() would be good to add.

 I set things up this way because I didn't want to bloat branch-list.js,
 in fact, I don't even need it in my app at all.

 Anyway, the extension looks useful, and I look forward to giving it a
 try soon.

 Adam

 On Wed, May 11, 2016 at 11:12 AM, Alexei Peters 
 wrote:

> Hi Angela,
> It's great that you guys were able to extend Arches v3 to support
> fuzzy dates.  Including fuzzy dates natively has definitely been on our
> radar and will be included in v4.
> Thanks for contributing back to the community!
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. -
> 971.227.3173
>
> On Fri, May 6, 2016 at 2:17 PM, Angela Labrador 
> wrote:
>
>> Greetings!
>>
>> While learning how Arches works and testing it out in house, we found
>> that adding Extended Date/Time Format
>> support
>> to Arches date fields would possibly benefit users who need to manage a
>> wider range of dates in their inventory system: dates such as "about 
>> 1800"
>> or date ranges such as "1934 - present".
>>
>> We've developed a validation function that can handle such date
>> strings while maintaining consistency and basic integrity for search in
>> Arches. The feature is available to the community at our Github
>> repository along with more detailed technical documentation
>>  for installing and
>> testing. Our recent blo

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Joel Aldor]

Hi Alexei,

This is something we're really looking forward to. Thanks a lot!

Regards,

Joel

On Saturday, July 22, 2017 at 2:18:20 AM UTC+8, Alexei Peters wrote:
>
> Hi Vincent,
> Here's the status of dates and the collection of date information in v4.
> As it stands v4.0.0 will only be able to collect date information in the 
> few specific formats that you mention above: -MM-DD, -MM and  
> If you only want to collect  then you need to remember to set the 
> format in the Card Designer (see attached screen shot).  I've verified that 
> this will not add -01-01 to the date saved.
> As for the backend validation, we will try to sync that up before the 
> release of v4.
>
> In the very near future(next couple of months) we will be addressing the 
> "fuzzy date" issue so that users can collect anything that relates to a 
> point or range of time and that won't force users to enter specific 
> formats.  Eg: you could just specify the string  '*late third century 
> B.C.*'
> Allowing something like this to participate in search will be the real 
> trick, but I think it's at least partially achievable!
>
> Hope this helps.
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Tue, Jul 18, 2017 at 4:14 AM, Vincent Meijer  > wrote:
>
>> Hi Alexei,
>>
>> What is the current status of fuzzy dates in Arches 4? 
>>
>> I have been looking at the Arches code, and it seems the frontend 
>> DatePicker only allows -MM-DD, -MM and  (*but no B.C.*).
>> However, in practice the datepicker automatically adds 01-01 when I only 
>> enter a year.
>> The backend seems to have it's own date 
>> validation: '-%Y','%Y','%Y-%m-%d','%B-%m-%d','%Y-%m-%d %H:%M:%S'
>>
>> I think being able to specify years only and B.C. years would be a good 
>> start for our use case, but this would require that our users translate 
>> '*late 
>> third century B.C.*' to something like '*-210*'. Seems sketchy. 
>>
>> However, I just started thinking about this and maybe there are better 
>> solutions. Thoughts welcome!
>>
>> Thanks!
>> Vincent
>>
>>
>> On Tuesday, 17 May 2016 17:57:30 UTC+2, Angela Labrador wrote:
>>
>>> Good thought, Adam - thanks for the feedback -- and great news that 
>>> native support for a broader range of date types will be in version 4! 
>>>
>>> On Wednesday, May 11, 2016 at 7:28:09 PM UTC-4, Adam Cox wrote:

 Hi Angela, this looks good and I appreciate the detailed documentation 
 on how to install the extension.

 One thought I had is that you could move your validation into a new 
 dedicated file, and then leave branch-list.js alone.  I did this in my 
 current project, in order to create a centralized location for validation 
 functions so I could apply them in any form. I created validation.js 
 ,
  
 and then used it in each form like this 
 
  
 (see lines 5, 9, and 80).  I have two basic functions in there now, but 
 have thought that a simple nodeIsDigit() would be good to add.

 I set things up this way because I didn't want to bloat branch-list.js, 
 in fact, I don't even need it in my app at all.

 Anyway, the extension looks useful, and I look forward to giving it a 
 try soon.

 Adam

 On Wed, May 11, 2016 at 11:12 AM, Alexei Peters  
 wrote:

> Hi Angela,
> It's great that you guys were able to extend Arches v3 to support 
> fuzzy dates.  Including fuzzy dates natively has definitely been on our 
> radar and will be included in v4.
> Thanks for contributing back to the community!
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 
> 971.227.3173
>
> On Fri, May 6, 2016 at 2:17 PM, Angela Labrador  
> wrote:
>
>> Greetings!
>>
>> While learning how Arches works and testing it out in house, we found 
>> that adding Extended Date/Time Format 
>> support 
>> to Arches date fields would possibly benefit users who need to manage a 
>> wider range of dates in their inventory system: dates such as "about 
>> 1800" 
>> or date ranges such as "1934 - present". 
>>
>> We've developed a validation function that can handle such date 
>> strings while maintaining consistency and basic integrity for search in 
>> Arches. The feature is available to the community at our Github 
>> repository along with more detailed technical documentation 
>>  for installing and 
>> testing. Our recent blog article 
>>  provides some 
>> background as well.

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Alexei Peters]

Hi Vincent,
Here's the status of dates and the collection of date information in v4.
As it stands v4.0.0 will only be able to collect date information in the
few specific formats that you mention above: -MM-DD, -MM and 
If you only want to collect  then you need to remember to set the
format in the Card Designer (see attached screen shot).  I've verified that
this will not add -01-01 to the date saved.
As for the backend validation, we will try to sync that up before the
release of v4.

In the very near future(next couple of months) we will be addressing the
"fuzzy date" issue so that users can collect anything that relates to a
point or range of time and that won't force users to enter specific
formats.  Eg: you could just specify the string  '*late third century B.C.*'
Allowing something like this to participate in search will be the real
trick, but I think it's at least partially achievable!

Hope this helps.
Cheers,
Alexei


Director of Web Development - Farallon Geographics, Inc. - 971.227.3173

On Tue, Jul 18, 2017 at 4:14 AM, Vincent Meijer 
wrote:

> Hi Alexei,
>
> What is the current status of fuzzy dates in Arches 4?
>
> I have been looking at the Arches code, and it seems the frontend
> DatePicker only allows -MM-DD, -MM and  (*but no B.C.*).
> However, in practice the datepicker automatically adds 01-01 when I only
> enter a year.
> The backend seems to have it's own date validation: 
> '-%Y','%Y','%Y-%m-%d','%B-%m-%d','%Y-%m-%d
> %H:%M:%S'
>
> I think being able to specify years only and B.C. years would be a good
> start for our use case, but this would require that our users translate '*late
> third century B.C.*' to something like '*-210*'. Seems sketchy.
>
> However, I just started thinking about this and maybe there are better
> solutions. Thoughts welcome!
>
> Thanks!
> Vincent
>
>
> On Tuesday, 17 May 2016 17:57:30 UTC+2, Angela Labrador wrote:
>
>> Good thought, Adam - thanks for the feedback -- and great news that
>> native support for a broader range of date types will be in version 4!
>>
>> On Wednesday, May 11, 2016 at 7:28:09 PM UTC-4, Adam Cox wrote:
>>>
>>> Hi Angela, this looks good and I appreciate the detailed documentation
>>> on how to install the extension.
>>>
>>> One thought I had is that you could move your validation into a new
>>> dedicated file, and then leave branch-list.js alone.  I did this in my
>>> current project, in order to create a centralized location for validation
>>> functions so I could apply them in any form. I created validation.js
>>> ,
>>> and then used it in each form like this
>>> 
>>> (see lines 5, 9, and 80).  I have two basic functions in there now, but
>>> have thought that a simple nodeIsDigit() would be good to add.
>>>
>>> I set things up this way because I didn't want to bloat branch-list.js,
>>> in fact, I don't even need it in my app at all.
>>>
>>> Anyway, the extension looks useful, and I look forward to giving it a
>>> try soon.
>>>
>>> Adam
>>>
>>> On Wed, May 11, 2016 at 11:12 AM, Alexei Peters 
>>> wrote:
>>>
 Hi Angela,
 It's great that you guys were able to extend Arches v3 to support fuzzy
 dates.  Including fuzzy dates natively has definitely been on our radar and
 will be included in v4.
 Thanks for contributing back to the community!
 Cheers,
 Alexei


 Director of Web Development - Farallon Geographics, Inc. - 971.227.3173

 On Fri, May 6, 2016 at 2:17 PM, Angela Labrador 
 wrote:

> Greetings!
>
> While learning how Arches works and testing it out in house, we found
> that adding Extended Date/Time Format
> support to
> Arches date fields would possibly benefit users who need to manage a wider
> range of dates in their inventory system: dates such as "about 1800" or
> date ranges such as "1934 - present".
>
> We've developed a validation function that can handle such date
> strings while maintaining consistency and basic integrity for search in
> Arches. The feature is available to the community at our Github
> repository along with more detailed technical documentation
>  for installing and
> testing. Our recent blog article
>  provides some
> background as well.
>
> Please try it out -- we welcome all contributions and issue reports at
> our repo!
>
> Hope this helps out some folks,
> Angela Labrador, PhD.
> Coherit Associates, LLC
>
> --
> -- To post, send email to arches...@googlegroups.com. To unsubscribe,
> send email to archesprojec...@googlegroups.com. For more information,
> 

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Vincent Meijer]

Hi Alexei,

What is the current status of fuzzy dates in Arches 4? 

I have been looking at the Arches code, and it seems the frontend 
DatePicker only allows -MM-DD, -MM and  (*but no B.C.*).
However, in practice the datepicker automatically adds 01-01 when I only 
enter a year.
The backend seems to have it's own date 
validation: '-%Y','%Y','%Y-%m-%d','%B-%m-%d','%Y-%m-%d %H:%M:%S'

I think being able to specify years only and B.C. years would be a good 
start for our use case, but this would require that our users translate '*late 
third century B.C.*' to something like '*-210*'. Seems sketchy. 

However, I just started thinking about this and maybe there are better 
solutions. Thoughts welcome!

Thanks!
Vincent


On Tuesday, 17 May 2016 17:57:30 UTC+2, Angela Labrador wrote:

> Good thought, Adam - thanks for the feedback -- and great news that native 
> support for a broader range of date types will be in version 4! 
>
> On Wednesday, May 11, 2016 at 7:28:09 PM UTC-4, Adam Cox wrote:
>>
>> Hi Angela, this looks good and I appreciate the detailed documentation on 
>> how to install the extension.
>>
>> One thought I had is that you could move your validation into a new 
>> dedicated file, and then leave branch-list.js alone.  I did this in my 
>> current project, in order to create a centralized location for validation 
>> functions so I could apply them in any form. I created validation.js 
>> ,
>>  
>> and then used it in each form like this 
>> 
>>  
>> (see lines 5, 9, and 80).  I have two basic functions in there now, but 
>> have thought that a simple nodeIsDigit() would be good to add.
>>
>> I set things up this way because I didn't want to bloat branch-list.js, 
>> in fact, I don't even need it in my app at all.
>>
>> Anyway, the extension looks useful, and I look forward to giving it a try 
>> soon.
>>
>> Adam
>>
>> On Wed, May 11, 2016 at 11:12 AM, Alexei Peters  
>> wrote:
>>
>>> Hi Angela,
>>> It's great that you guys were able to extend Arches v3 to support fuzzy 
>>> dates.  Including fuzzy dates natively has definitely been on our radar and 
>>> will be included in v4.
>>> Thanks for contributing back to the community!
>>> Cheers,
>>> Alexei
>>>
>>>
>>> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>>>
>>> On Fri, May 6, 2016 at 2:17 PM, Angela Labrador  
>>> wrote:
>>>
 Greetings!

 While learning how Arches works and testing it out in house, we found 
 that adding Extended Date/Time Format 
 support to 
 Arches date fields would possibly benefit users who need to manage a wider 
 range of dates in their inventory system: dates such as "about 1800" or 
 date ranges such as "1934 - present". 

 We've developed a validation function that can handle such date strings 
 while maintaining consistency and basic integrity for search in Arches. 
 The 
 feature is available to the community at our Github repository along 
 with more detailed technical documentation 
  for installing and 
 testing. Our recent blog article 
  provides some 
 background as well. 

 Please try it out -- we welcome all contributions and issue reports at 
 our repo!

 Hope this helps out some folks,
 Angela Labrador, PhD.
 Coherit Associates, LLC

 -- 
 -- To post, send email to arches...@googlegroups.com. To unsubscribe, 
 send email to archesprojec...@googlegroups.com. For more information, 
 visit https://groups.google.com/d/forum/archesproject?hl=en
 --- 
 You received this message because you are subscribed to the Google 
 Groups "Arches Project" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to archesprojec...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> -- 
>>> -- To post, send email to arches...@googlegroups.com. To unsubscribe, 
>>> send email to archesprojec...@googlegroups.com. For more information, 
>>> visit https://groups.google.com/d/forum/archesproject?hl=en
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Arches Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to archesprojec...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
Yo

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Angela Labrador]

Good thought, Adam - thanks for the feedback -- and great news that native 
support for a broader range of date types will be in version 4! 

On Wednesday, May 11, 2016 at 7:28:09 PM UTC-4, Adam Cox wrote:
>
> Hi Angela, this looks good and I appreciate the detailed documentation on 
> how to install the extension.
>
> One thought I had is that you could move your validation into a new 
> dedicated file, and then leave branch-list.js alone.  I did this in my 
> current project, in order to create a centralized location for validation 
> functions so I could apply them in any form. I created validation.js 
> ,
>  
> and then used it in each form like this 
> 
>  
> (see lines 5, 9, and 80).  I have two basic functions in there now, but 
> have thought that a simple nodeIsDigit() would be good to add.
>
> I set things up this way because I didn't want to bloat branch-list.js, in 
> fact, I don't even need it in my app at all.
>
> Anyway, the extension looks useful, and I look forward to giving it a try 
> soon.
>
> Adam
>
> On Wed, May 11, 2016 at 11:12 AM, Alexei Peters  > wrote:
>
>> Hi Angela,
>> It's great that you guys were able to extend Arches v3 to support fuzzy 
>> dates.  Including fuzzy dates natively has definitely been on our radar and 
>> will be included in v4.
>> Thanks for contributing back to the community!
>> Cheers,
>> Alexei
>>
>>
>> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>>
>> On Fri, May 6, 2016 at 2:17 PM, Angela Labrador > > wrote:
>>
>>> Greetings!
>>>
>>> While learning how Arches works and testing it out in house, we found 
>>> that adding Extended Date/Time Format 
>>> support to 
>>> Arches date fields would possibly benefit users who need to manage a wider 
>>> range of dates in their inventory system: dates such as "about 1800" or 
>>> date ranges such as "1934 - present". 
>>>
>>> We've developed a validation function that can handle such date strings 
>>> while maintaining consistency and basic integrity for search in Arches. The 
>>> feature is available to the community at our Github repository along 
>>> with more detailed technical documentation 
>>>  for installing and 
>>> testing. Our recent blog article 
>>>  provides some 
>>> background as well. 
>>>
>>> Please try it out -- we welcome all contributions and issue reports at 
>>> our repo!
>>>
>>> Hope this helps out some folks,
>>> Angela Labrador, PhD.
>>> Coherit Associates, LLC
>>>
>>> -- 
>>> -- To post, send email to arches...@googlegroups.com . To 
>>> unsubscribe, send email to archesprojec...@googlegroups.com 
>>> . For more information, visit 
>>> https://groups.google.com/d/forum/archesproject?hl=en
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Arches Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to archesprojec...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> -- To post, send email to arches...@googlegroups.com . To 
>> unsubscribe, send email to archesprojec...@googlegroups.com . 
>> For more information, visit 
>> https://groups.google.com/d/forum/archesproject?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Arches Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to archesprojec...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Adam Cox]

Hi Angela, this looks good and I appreciate the detailed documentation on
how to install the extension.

One thought I had is that you could move your validation into a new
dedicated file, and then leave branch-list.js alone.  I did this in my
current project, in order to create a centralized location for validation
functions so I could apply them in any form. I created validation.js
,
and then used it in each form like this

(see lines 5, 9, and 80).  I have two basic functions in there now, but
have thought that a simple nodeIsDigit() would be good to add.

I set things up this way because I didn't want to bloat branch-list.js, in
fact, I don't even need it in my app at all.

Anyway, the extension looks useful, and I look forward to giving it a try
soon.

Adam

On Wed, May 11, 2016 at 11:12 AM, Alexei Peters  wrote:

> Hi Angela,
> It's great that you guys were able to extend Arches v3 to support fuzzy
> dates.  Including fuzzy dates natively has definitely been on our radar and
> will be included in v4.
> Thanks for contributing back to the community!
> Cheers,
> Alexei
>
>
> Director of Web Development - Farallon Geographics, Inc. - 971.227.3173
>
> On Fri, May 6, 2016 at 2:17 PM, Angela Labrador  wrote:
>
>> Greetings!
>>
>> While learning how Arches works and testing it out in house, we found
>> that adding Extended Date/Time Format
>> support to
>> Arches date fields would possibly benefit users who need to manage a wider
>> range of dates in their inventory system: dates such as "about 1800" or
>> date ranges such as "1934 - present".
>>
>> We've developed a validation function that can handle such date strings
>> while maintaining consistency and basic integrity for search in Arches. The
>> feature is available to the community at our Github repository along
>> with more detailed technical documentation
>>  for installing and testing.
>> Our recent blog article
>>  provides some
>> background as well.
>>
>> Please try it out -- we welcome all contributions and issue reports at
>> our repo!
>>
>> Hope this helps out some folks,
>> Angela Labrador, PhD.
>> Coherit Associates, LLC
>>
>> --
>> -- To post, send email to archesproject@googlegroups.com. To
>> unsubscribe, send email to archesproject+unsubscr...@googlegroups.com.
>> For more information, visit
>> https://groups.google.com/d/forum/archesproject?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Arches Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to archesproject+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> -- To post, send email to archesproject@googlegroups.com. To unsubscribe,
> send email to archesproject+unsubscr...@googlegroups.com. For more
> information, visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Arches Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to archesproject+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Alexei Peters]

Hi Angela,
It's great that you guys were able to extend Arches v3 to support fuzzy
dates.  Including fuzzy dates natively has definitely been on our radar and
will be included in v4.
Thanks for contributing back to the community!
Cheers,
Alexei


Director of Web Development - Farallon Geographics, Inc. - 971.227.3173

On Fri, May 6, 2016 at 2:17 PM, Angela Labrador  wrote:

> Greetings!
>
> While learning how Arches works and testing it out in house, we found that
> adding Extended Date/Time Format
> support to
> Arches date fields would possibly benefit users who need to manage a wider
> range of dates in their inventory system: dates such as "about 1800" or
> date ranges such as "1934 - present".
>
> We've developed a validation function that can handle such date strings
> while maintaining consistency and basic integrity for search in Arches. The
> feature is available to the community at our Github repository along with
> more detailed technical documentation
>  for installing and testing.
> Our recent blog article
>  provides some
> background as well.
>
> Please try it out -- we welcome all contributions and issue reports at our
> repo!
>
> Hope this helps out some folks,
> Angela Labrador, PhD.
> Coherit Associates, LLC
>
> --
> -- To post, send email to archesproject@googlegroups.com. To unsubscribe,
> send email to archesproject+unsubscr...@googlegroups.com. For more
> information, visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Arches Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to archesproject+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Arches] Supporting "fuzzy dates", approximations, and uncertain dates in Arches

[Angela Labrador]

Greetings!

While learning how Arches works and testing it out in house, we found that 
adding Extended Date/Time Format 
support to 
Arches date fields would possibly benefit users who need to manage a wider 
range of dates in their inventory system: dates such as "about 1800" or 
date ranges such as "1934 - present". 

We've developed a validation function that can handle such date strings 
while maintaining consistency and basic integrity for search in Arches. The 
feature is available to the community at our Github repository along with 
more detailed technical documentation 
 for installing and testing. 
Our recent blog article 
 provides some 
background as well. 

Please try it out -- we welcome all contributions and issue reports at our 
repo!

Hope this helps out some folks,
Angela Labrador, PhD.
Coherit Associates, LLC

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.