Dear Developers -- and all you seasoned users :-) We are going to use arches3 / arches-hip as a database on archaeological sites in Greece and Turkey. For this purpose we need to adapt Resource Graphs in arches-hip to accomodate new fields.
Dennis Wuthrich already supplied us with the following hints (thank you, Dennis). I am putting the question to the forum as I hope it will foster crowd-intelligence: You can modify these graphs, or create new graphs to meet your data > management demands. This work is done outside Arches. In other words, you > just need to create the nodes and edges file that are required to define a > graph that meets your requirements. There are some very simple rules to > creating graphs for Arches, most of which you can infer simply by looking > at the nodes/edges files that come with Arches. > This step is quite clear to us (at least we think so, before having really started) One thing to know: once you create new graphs you will need to create new > data entry forms (or perhaps modify existing forms). You’ll probably also > want to create or modify Arches’ default graph reports too. This will > require that you or your project team members are familiar with a bit of > python, javascript, and html As far as I understand, arches "ends" when it comes to provide / adapt forms and reports for the business data. But maybe there is slightly more information available on how actually proceed with these necessary adaptations in arches' python / javascript and html code? In the online-documentation there are some placeholders for "Forms" and "Reports" -- is there any chance to get some preliminary pieces of documentation on that already? Anybody out there who already made changes to arches' Resource-Graphs and went through the subsequent adaptations in the code? A more specific question: I am not really familar with Django yet, therefore I have to ask a probably "naive" question: to which extent does arches rest on Django? Will the necessary adaptations become clear / obvious / trivial :-) for anybody with a sounder knowledge of Django, or will we always need to go through the whole source-code of arches in order to build up the necessary understanding of implementation-details? Finally we will have to plunge into the code, I know, but I am still hoping we won't have to do it blindly :-) Many thanks & all the best Hannes -- -- 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.
