(...) and by the way, I did manage to enter some resource data without 
accessing the authority files, namely location (.kml) and names, but not 
the other types.


terça-feira, 6 de Dezembro de 2016 às 10:43:14 UTC, David Lopes escreveu:
>
> Hi Adam,
>
> I know now what was the problem: when running the *manage.py* command I 
> didn't include the path to the authority files. 
>
> I now have under Arches all the menus those files provide, just had to run  
> *$ 
> python manage.py packages -o load_concept_scheme -s 'path to authority 
> files directory' *as mentioned in arches-hip documentation.
>
> Regards,
>
>
>
>
>
> segunda-feira, 5 de Dezembro de 2016 às 16:36:04 UTC, Adam Cox escreveu:
>>
>> Hi David, I'm a little confused at this point. If you only have one entry 
>> (Resource to Resource Relationships) listed in the RDM, how are you able to 
>> enter data? It sounds like none of the dropdown menus would be available to 
>> you, which 
>> would make it impossible to add those attributes to new resources.
>>
>> Going back to my previous message, where I included the command to load 
>> concept schemes, I was just dealing with this over the weekend, and 
>> realized there is one other setting to change before running that command. 
>>  In your *app's* settings.py file, find the line that says 
>> CONCEPT_SCHEME_LOCATIONS. I think you'll find that it is currently 
>> setting that variable back to (), which will overwrite the change I 
>> asked you to make in the ..\ENV\Lib\site-packages\arches_hip settings.py 
>> file. So, just comment out the entire CONCEPT_SCHEME_LOCATIONS line in 
>> your app's settings.py file, and then try
>> python manage.py packages -o load_concept_scheme
>> (with your virtual environment activated) once more. I think that will 
>> solve your problem.
>>
>> Hope that all makes sense, and let me know how it goes.
>>
>> Adam
>>
>>
>>
>> On Friday, December 2, 2016 at 10:29:32 AM UTC-6, David Lopes wrote:
>>>
>>> (...)
>>>
>>> Yes it worked, but in RDM, under Arches, I still only get the item 
>>> "Resource 
>>> To Resource Relationship Types".
>>> I assume it's ok, I'll proceed cataloguing the resources and then report 
>>> to you if necessary.
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>> sexta-feira, 2 de Dezembro de 2016 às 15:59:34 UTC, David Lopes escreveu:
>>>>
>>>> Hi Adam,
>>>>
>>>> I've done as you indicate, but I get the following message:
>>>>
>>>>
>>>>
>>>>
>>>> *Traceback (most recent call last):  File "manage.py", line 22, in 
>>>> <module>    from django.core.management import 
>>>> execute_from_command_lineImportError: No module named 
>>>> django.core.management*
>>>>
>>>> Can you please tell me what's wrong.
>>>>
>>>> Regards,
>>>>
>>>> terça-feira, 8 de Novembro de 2016 às 20:41:39 UTC, Adam Cox escreveu:
>>>>>
>>>>> Hi David, when you installed Arches, did you use any authority files? 
>>>>> Doing so will populate the RDM with the default concepts/dropdown menu 
>>>>> contents, and will give you options when you try to choose a Historic 
>>>>> Resource Type, as you are doing.
>>>>>
>>>>> You'll know for sure if you enter the RDM and can find a long list of 
>>>>> entries underneath the Arches menu in the left pane. If you only have one 
>>>>> *Resource 
>>>>> To Resource Relationship Types* entry, then the authority files have 
>>>>> not loaded. The easiest way to fix this would be to go into your ENV (on 
>>>>> Windows ..\ENV\Lib\site-packages\arches_hip) and make a very slight 
>>>>> modification to settings.py: just uncomment this line 
>>>>> https://github.com/archesproject/hip/blob/master/arches_hip/settings.py#L153,
>>>>>  
>>>>> which will set the CONCEPT_SCHEME_LOCATIONS variable to point to the 
>>>>> authority documents that ship with arches_hip. Then run
>>>>> python manage.py packages -o load_concept_scheme
>>>>> and all of the controlled vocabularies should be loaded into Arches.
>>>>>
>>>>> Now you should see values in all of the dropdown data entry widgets, 
>>>>> and you should see a long list of concept schemes in the RDM.
>>>>>
>>>>> Hopefully that helps!
>>>>> Adam
>>>>>
>>>>> On Thursday, November 3, 2016 at 6:03:10 AM UTC-5, David Lopes wrote:
>>>>>>
>>>>>> Hi Adam,
>>>>>>
>>>>>> To give you an example:
>>>>>>
>>>>>> I'm not  able to fill *Historic Resource Type* field in the *Resource 
>>>>>> Summary*.
>>>>>>
>>>>>> In  Tools/Reference Data Manager (RDM) I added a Scheme named *Historic 
>>>>>> Resource Type* which appears on the menu's root but then there's no 
>>>>>> dropdown entry.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> David L
>>>>>>
>>>>>> segunda-feira, 31 de Outubro de 2016 às 04:53:44 UTC, Adam Cox 
>>>>>> escreveu:
>>>>>>>
>>>>>>> Hi David, I'm assuming you've already checked out the Arches v3 
>>>>>>> documentation on the RDM? 
>>>>>>> http://arches3.readthedocs.io/en/latest/rdm/. Currently, that is 
>>>>>>> the best place for RDM-specific documentation. As for this question, 
>>>>>>> could 
>>>>>>> you be more specific about the problem you're having? Are you adding 
>>>>>>> the 
>>>>>>> resource through the data entry forms, or importing with a .arches 
>>>>>>> file? If 
>>>>>>> the former, is does the desired resource type show up in the form 
>>>>>>> dropdown?
>>>>>>>
>>>>>>> Adam
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, October 27, 2016 at 9:02:47 AM UTC-5, David Lopes wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> When trying to add a new historic resource it never accepts the 
>>>>>>>> *historic 
>>>>>>>> resource type* that I define. What in RDM do I have to tweak to 
>>>>>>>> accept this definition?
>>>>>>>>
>>>>>>>> Where can I find further instructions on how to work with RDM ?
>>>>>>>>
>>>>>>>> Regards.
>>>>>>>>
>>>>>>>

-- 
-- 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