Hi Adam,

I have a couple of basic 'Arches-HIP' installation question. In the 
'Arches-HIP' installation document 

http://arches-hip.readthedocs.org/en/latest/getting-started/#installation

among the dependencies I did not find any mentioning of Django. I did 
install everything else, including Python 2.7.6. But when running 
'arches-app create' part, I received an error, which was attributed to the 
wrong version of Django. The version which I installed is 1.9.4. And the 
error was in line 11 of the 'arches-app' file. When I googled it, I found 
that instead of deprecated in version 1.9.4
 

*from django.utils.importlib import import_module*

it should be 

*from django.utils.module_loading import import_module*

which did fix this immediate issue for me. So my question: is there a 
specific version of Django that is recommended for the installation? 

And one more thing. After running 'arches-app create' the folder 
'my_hip_app' was created, but the only one file in that folder was 
'.hgignore' and nothing else. And I got this error message: 

File "C:\Projects\ENV\lib\site-packages\django\apps\registry.py", line 124, 
in
 check_apps_ready
    raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

What could be wrong? Thank you in advance for your answer. Sorry If the 
questions are too basic, I am just starting to work on 'Arches' and am new 
to Django too.

Viktor Grabarchuk

On Wednesday, December 30, 2015 at 3:26:35 PM UTC-8, Adam Cox wrote:

> Hi Lucy, good question. I could have been more clear on that point.
>
> Changes to the resource graphs require a reinstallation of your custom 
> Arches app. So, the steps I would recommend are
> 1. Install arches and arches-HIP
> 2. Create a new app as directed in the documentation
> 3. Fully install this app (after elasticsearch is setup, etc.) with:
> python manage.py packages -o install
> 4. Run the development server to make sure the app is working. It will be 
> the default arches-HIP app.
> 5. Now, spend time modifying the resource graphs and authority files as 
> much as you need.
> 6. Whenever you feel ready, run the install command shown above again.  
> The previous database will be deleted and one that uses the new resource 
> graph schema will replace it. This is what I meant by "database 
> reinstallation", but I could have chosen better wording so I'll see what I 
> can do to correct that.
> 7. When you have the new schema set, you can begin modifying the forms and 
> reports to support the new nodes.  Changing these templates does not 
> require a reinstallation though--you can do it anytime.
>
> Hope that answers your question! Let me know if you need anymore 
> clarification.
> Adam
> On Dec 30, 2015 5:07 AM, "Lucy FJ" <[email protected] <javascript:>> 
> wrote:
>
>> Hi Alison and Adam,
>>
>> I hope you have enjoyed/are enjoying the festive season! 
>>
>> This is a very useful document to have - thank you, Adam -  and as we are 
>> just about a reinstall the latest release of Arches and make 
>> customizations, (and remove our test data) I just wish to clarify the order 
>> of events when customizing Arches. The document states that: 
>> *Changes to the resource graphs will require a database reinstall, and 
>> possibly new controlled vocabularies, so this effort should be made at the 
>> beginning of the installation process.* 
>> Does this mean we must update the graphs before reinstalling the new 
>> release of Arches, or of  Arches HIP, or before inputting any heritage 
>> resource data? 
>>
>>
>> Thank you very much for clarifying. 
>> Lucy
>>
>> On Friday, October 23, 2015 at 4:46:46 AM UTC+2, Alison Dalgity wrote:
>>>
>>> Greetings all.
>>>
>>>
>>> We have just posted a list of considerations that we hope will be 
>>> helpful, especially if you are planning to evaluate or implement Arches. 
>>>
>>> See: http://archesproject.org/implementation-considerations/
>>>
>>>
>>> This document was kindly created by Adam Cox based on his experience as 
>>> a lone implementor of Arches in Louisiana. It is a living document that we 
>>> hope will be updated and expanded as we all gain more experience with 
>>> future implementations of Arches.
>>>
>>>
>>> Please take a look and let us know your thoughts.
>>>
>>>
>>> Alison
>>>
>> -- 
>> -- To post, send email to [email protected] <javascript:>. To 
>> unsubscribe, send email to [email protected] <javascript:>. 
>> 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] <javascript:>.
>> 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.

Reply via email to