Here's a forum thread related to editing resource graphs, and if you dig
you should be able to find more for specific tasks.
https://groups.google.com/forum/#!searchin/archesproject/form/archesproject/PFshiztyAYE/PJPKa8X8DQAJ
Ultimately, you're on the right path, but there are a number of steps
involved.
Prepwork:
1. Move the views/resource.py and views/forms.py files from Arches-HIP to
your own app
2. In your settings.py set the path to the new resource model (your new
resource.py file)
3. In the resource.py file, change the forms import statement to get the
local 'forms' module, not the arches_hip.forms
For each new/modified node
1. Modify the resource graph
2. Find the the appropriate form class in forms.py, and support the new
node in the load and update functions
3. Find the .htm and .js pair for the form in Arches-HIP and copy these to
your own app
--templates/views/forms/summary.htm
--media/js/views/forms/summary.js
4. Modify the branchlists in the .js file (which are supplied by the
forms.py class)
5. Modify the .htm file to use the correct node names
6. Find the report section that uses the new nodes and copy it from
arches_hip to your app
--templates/views/forms/sections
7. Make sure the new nodes are displayed in the report
It's a lot of coordination between files/languages. Feel free to look
through this app for examples: https://github.com/mradamcox/afrh (though my
.htm files are formatted a little differently).
Adam
On Wed, May 18, 2016 at 1:42 AM, Steven Jones <
[email protected]> wrote:
> Thanks for the replies!
>
> From poking around the codebase it looks like the Arches forms displayed
> in the web UI are defined in another file, yeah?
>
> So the process for customising Arches is to edit the resource graphs
> (currently by editing the files) and then also editing the forms file so
> that the correct fields are displayed in the correct ways etc. Is that
> correct?
>
>
>
> On Tuesday, May 17, 2016 at 5:25:54 PM UTC+1, Vincent Meijer wrote:
>>
>> Hi Steven,
>>
>> I'm trying to do something similar, although I have both mobile and
>> immobile objects.
>> I find that the resource graphs that come with Arches-HIP are pretty much
>> applicable to mobile (in my case mostly archaeological) objects as well,
>> particularly the one called Heritage Resource.
>> Its first field is Heritage Resource Type, where you can specify whether
>> it is an object or a building:
>> http://demo.archesproject.org/resources/HERITAGE_RESOURCE.E18/summary/
>>
>> What you can do is change the authority documents (these hold the values
>> you see in dropdown menus) so that they make sense for mobile objects.
>> E.g. expand the Heritage Resource Type dropdown menu so that it holds
>> your different types of mobile objects, for example coins.
>>
>> Further, I can imagine that under 'Important Dates', the date type
>> 'Creation date' would make sense for a coin.
>>
>>
>> You can *copy *the authority documents from Arches-HIP to your own
>> project folder:
>> *from *
>> arches_hip\arches_hip\source_data\sample_data\concepts\
>> sample_authority_files
>> *to *
>> my_hip_app\my_hip_app\source_data\concepts\authority_files
>>
>> and then make your customizations.
>>
>>
>> You could also go further and make customizations to the whole Heritage
>> Resource graph, for example to change the 'Components' section so that you
>> can specify the text and image on both sides of the coin as components.
>> http://demo.archesproject.org/resources/HERITAGE_RESOURCE.E18/component/
>>
>>
>>
>> The data structure I'm experimenting with looks something like:
>>
>> ACTIVITY: "Documenting the Smithsonian"
>> | relation: surveyed / was surveyed by
>> HERITAGE RESOURCE: "Smithsonian National Museum of African Art"
>> | relation: contains / is contained within
>> HERITAGE RESOURCE: "Gallery ground floor"
>> | relation: is occupied by / occupies
>> HERITAGE RESOURCE: "Ejagham Crest Mask"
>> | relation: is represented by / represents
>> INFORMATION RESOURCE: "photo of the mask"
>>
>>
>> Long story short, I prefer (and recommend) changing the existing
>> authority documents and resource graphs, rather than creating a new one
>> from the ground up.
>>
>> *If anyone else has ideas about how to best approach this, please let us
>> know!*
>>
>>
>> Hope this helps,
>>
>> Vincent
>>
>>
>> On Monday, 16 May 2016 04:48:26 UTC-4, Steven Jones wrote:
>>>
>>> Hi,
>>>
>>> I'm investigating using Arches for storing information about historical
>>> artifacts and events, rather than specifically places, as Arches-HIP
>>> provides.
>>>
>>> For example, I have a database of coins found in various locations by
>>> various people at various times. Ideally I'd like to store them in an
>>> Arches like system.
>>>
>>> Is there any work to provide a set of default graphs and reference data
>>> for storing such data.
>>>
>>> Arches-HIP seems very much geared toward storing data relating to
>>> immovable objects, which is fine, and great, just wondering if there's a
>>> project or fork of Arches-HIP somewhere that provides the same for moveable
>>> data.
>>>
>>>
>>> Regards
>>> Steven Jones
>>>
>> --
> -- 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.
>
--
-- 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.
