Hi Adam,

Thank you once again for looking into my problem. I confess that I have not 
looked very
hard at the actual graphs but at the lists in the appendices.
I do think that the naming of some of these authority files/entities is 
confusing and needs clarification,  perhaps in the user manual. 

When I'm back in the office on Sunday, I will change the drop down lists 
around. 

Thank you again for your invaluable help.
Lucy

Sent from my iPad

> On 28 Oct 2015, at 18:34, Adam Cox <[email protected]> wrote:
> 
> Hi Lucy, the main problem is that there are some semantic inconsistencies 
> between different pieces of the HIP.  I just checked these out, and here are 
> the "lineages" in question.  Keep in mind that the labels in the RDM are 
> based directly on the resource graph entity names:
> 
> 1)
> In the resource graph:
>   HERITAGE_RESOURCE.E18 > RESOURCE_TYPE_CLASSIFICATION.E55 > 
> RESOURCE_CLASSIFICATION_AUTHORITY_DOCUMENT.E32
> In the RDM:
>   Arches > Resource Classification
>   Dropdown Lists > Resource_Type_Classification.E55
> In the forms:
>   Resource Summary Form > Historic Resource Type
> 
> 2)
> In the resource graph:
>   HERITAGE_RESOURCE.E18 > PRODUCTION.E12 > PHASE_TYPE_ASSIGNMENT.E17 > 
> HERITAGE_RESOURCE_TYPE.E55 > HERITAGE_RESOURCE_TYPE_AUTHORITY_DOCUMENT.E32
> In the RDM:
>   Arches > Heritage Resource Type
>   Dropdown Lists > Heritage_Resource_Type.E55
> In the forms:
>   Classifications Form > Classification Summary (type)
> 
> So I'd say that techincally nothing is wrong, you just found a place where, 
> between the graphs and the forms, some terminology is being used in a 
> confusing manner.  If you end up digging into the forms, you could change the 
> names above the dropdowns with no trouble. It's definitely worth taking note 
> for future iterations of the HIP package.
> 
> Adam
> 
> 
> 
>> On Wednesday, October 28, 2015 at 3:03:55 AM UTC-5, Lucy FJ wrote:
>> 
>> 
>> 
>> Dear All,
>> 
>> I thought I'd start a new topic on this so as not to be confused with the 
>> other question I raised and has now been resolved. 
>> 
>>  I am only using the Reference DM to change the authority files because I am 
>> a user and we don't have a full time IT staff member assigned to our project 
>> yet so can't change the files directly.
>> I used the Arches HIP sample files as a basis and added our concepts for the 
>> heritage resource type and deleted the sample ones. I did the same for the 
>> resource classification types. I then added the appropriate concepts to the 
>> drop down lists for each. When I tried inputting a resource using the 
>> Resource Data manager, I found that the resource classification drop down 
>> list was where I expected the heritage resource list and vice versa. The 
>> concepts were the ones I had input. I have checked, double checked and 
>> triple checked my inputs and they are correct.
>> I am attaching copies of the screen shots.
>> 
>>   Has anyone come across this problem before?
>> 
>> Thank you for any help on this issue!
>> 
>> Lucy 
>> 
>> 
>> 
> 
> -- 
> -- 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 a topic in the Google 
> Groups "Arches Project" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/archesproject/q2FDw7fRwe8/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

Reply via email to