Hi Philippel, It sounds like what you are really asking for is this: What are the steps necessary to build an Arches Application (something different from the pre-made “HIP” application) that includes ontology beyond CIDOC CRM? In the interest of helping you get to where I think you are looking for, I’ll target my answer toward that question.
As a first step, you will want to define the resource graphs (http://arches3.readthedocs.org/en/latest/arches-data/#resource-graphs) that you want to load to Arches. The act of defining your resource graph(s) forces you to define what ontological classes and properties you wish to assign to each node in your graph. If you wish to apply classes and properties that are outside of the realm of CIDOC CRM, you will need to make Arches aware of these additional ontologies by loading them to the respective classes and properties tables within the ontology schema of the underlying database. The easiest way to do that is to update //arches/db/db_data.sql file. You will just have to add the insert statements necessary to account for these new classes and properties. After you have populated the Arches db with these new classes and properties, you then can load the graphs you built in the first step outlined above without errors. I believe the next major consideration will be around building the UI to interact with your custom resource graphs. Following the js examples provided in the HIP application should get you a long way on that, but others more knowledgeable than I in that area may want to chime in. I hope this helps. Best, Adam -- Adam Lodge Geospatial Systems Consultant Farallon Geographics On Wednesday, February 10, 2016 at 5:16 PM, Philippel wrote: > 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 [email protected] > (mailto:[email protected]). To unsubscribe, send email to > [email protected] > (mailto:[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] > (mailto:[email protected]). > For more options, visit https://groups.google.com/d/optout. -- -- 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.
