Daphne Ippolito writes:
>Even though I was not selected for GSoC, I am hoping that I can still
>make a contribution to Arches during my free time this summer. Of the
>tasks I mentioned in my proposal, I think that allowing Arches to
>store dates in a date type rather than a string type would be a
Even though I was not selected for GSoC, I am hoping that I can still make
a contribution to Arches during my free time this summer. Of the tasks I
mentioned in my proposal, I think that allowing Arches to store dates in a
date type rather than a string type would be a really useful improvement. I
Thanks for all your input!
I decided to go with the topic of improving Arches' ability to handle fuzzy
temporal endpoints.
I've submitted my proposal, and I look forward to hearing your opinions and
suggestions.
Best,
Daphne
On Monday, 17 March 2014 18:06:13 UTC-4, Koen Van Daele wrote:
>
> H
Hi Daphne,
I think that anything that has to deal with vague temporal or spatial
information will automatically turn out te be fairly complex.
The fuzzy endpoints of periods is probably the easier one. There the big hurdle
is making a good UI that allows for people to enter vague temporal infor
Hi Daphne,
I wanted to provide some input on two of the items you addressed in your
previous messages.
1. You asked if Arches supports sub-periods. The answer is yes. In fact
Arches supports any type of thesauri to have hierarchical relationships.
Whenever you hit a pick list in the UI (b
