Hello,
I am not sure if I should open a new thread with this, but it seems the right place to start. Considering implementation considerations. We are working on a regular basis with Django, so we have been mandated to evaluate costs of implementing Arches. The business experts are working with domain experts and ontological experts, so the how we get there, on the data side, if fairly well covered. What I can't figure out yet is the following. Given that the domain we have to integrate is wider than the CIDOC CRM ontology capabilities, we will need to integrate parts of other ontologies. Possibly create a proprietary ontology exploiting CIDOC and others. So basically not everything will be EXX and PYY, but I will have all the necessary conceptual model needed to generate the files and SQL to preload Arches and have the ontology data and thesaurus. What are the layers that will needed to be updated to implement the business logic that is outside of the Arches normal implementation? How complex is it, for a regular Django developer ? I have not look in details to the use of template done by Arches, but it seemed fairly straight forward. So I expect that as long as I have regular views and entities in the end, the integration of forms and security should be stream line work. Anyone as insight on this ? Thanks Philippe Laliberté -- -- 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.
