Dear all, Is it possible to use and to easily create and query numeric fields within ARCHES v3?
I am working for a project at the moment that has been using ARCHES v3 for a number of years and all of the dating is handled as text fields e.g. 'Roman', 'Iron Age' etc. This is causing us problems when we want to implement our database in partner countries that use different labeling systems. One solution would be to use integer fields for start and end dates. I have worked on other databases in the past which have made use of negative integers for BC dates and positive integers for AD dates. I am being told, however, by our IT support that ARCHES cannot support this? To be precise I am being told that I myself would have to write the front-end and back-end logic to handle the fields that I would like to implement. That is, some new code would have to be written in order to handle a numeric search in ARCHES v3. Obviously the integer fields can be created in postgres and I am comfortable with how to do this, but I really need some step-by-step help in order to understand how to get ARCHES to integrate with such fields. To give you an idea of the scale of the problem, in the midst of the discussion about chronology I have realized that all of the fields currently being used in the project database avoid the use of integers. Numbers of archaeological features are recorded as text e.g. 1 to 5, 6-20, or 21-50! This leaves us with no way of querying in a quantified way e.g. Return all sites where number of theatres is greater than 1. Any help with this issue would be most appreciated. Matt Hobson -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
