Hi Adam, Thank you very much for your help! Your explanation makes sense. My apologies for the confusion.
yikang On Friday, December 18, 2015 at 11:53:51 PM UTC+8, Adam Cox wrote: > > Hi Yikang, glad to hear you were able to get Arches up and running. > > The simple answer is that just like a value for NAME_TYPE.E55 in the > .arches file must correspond to a conceptid in the > NAME_TYPE_AUTHORITY_DOCUMENT.E32, a RELATION_TYPE in the .relations file > must correspond to a relationship type that is defined in the relationship > type authority document. If you loaded the sample authority documents from > Arches-HIP, then you have already loaded the file in question, and it looks > like you've found an error in the documentation. Here's the file > <https://bitbucket.org/arches/hip/src/8d3ec0e6643d11c2606992f4c7ed80d912acd3d5/arches_hip/source_data/sample_data/concepts/sample_authority_files/ARCHES%20RESOURCE%20CROSS-REFERENCE%20RELATIONSHIP%20TYPES.E32.csv?at=default&fileviewer=file-view-default>, > > so it looks like it's just mislabeled in the directions that you > referenced. I'll update that... > > So to answer your questions specifically: > 1) conceptid,PrefLabel,AltLabels,ParentConceptid,ConceptType,Provider (see > linked example above) > 2) Yes, and it is already included in the HIP authority files, but it is > named ARCHES RESOURCE CROSS-REFERENCE RELATIONSHIP TYPES.E32.csv > 3) No, you just need this single line in the ENTITY_TYPE_X_ADOC.csv > (shown in red below): > entitytype,authoritydoc,authoritydocconceptscheme > ARCHES_RESOURCE_CROSS-REFERENCE_RELATIONSHIP_TYPES.E55,ARCHES RESOURCE > CROSS-REFERENCE RELATIONSHIP TYPES.E32.csv,yourconceptschemename > 4) No, the "properties" referenced in the CIDOC CRM are connections > between nodes within a single instance of a resource (as you can see in the > resource graphs). The "relations" that are defined in the .relations file > are connections between different resource instances. If you open the > HERITAGE_RESOURCE.E18 resource graph and the ACTOR.E39 resource graph, you > could imagine a "relation" as a line between the central nodes of each > graph. > > Hope that makes sense. > > EDIT: It looks like the documentation was correct, but somehow when the > highlighting was added a new space appeared, turning RELATIONSHIP into > RELATIONS HIP. A strange confusion. > > Adam > > On Friday, December 18, 2015 at 3:56:09 AM UTC-6, YK Feng wrote: >> >> Hello all, >> >> I'm an academic librarian from Singapore and am exploring using Arches >> HIP for Digital Humanities. Thank you for this wonderful product and the >> clear &comprehensive documentation. >> >> I just installed Arches HIP, and have successfully added one set of test >> data. I'm now exploring adding of relations. >> >> In this page of the documentation >> http://arches3.readthedocs.org/en/latest/arches-data/?highlight=relations >> it was mentioned: >> >> The .relations file is a pipe (|) delimited text file containing the >> following column headers: >> >> >> - RESOURCEID_FROM indicates one of the two resources to be related. >> The value here must also be present as a RESOURCEID in the .arches >> file. >> - RESOURCEID_TO indicates the other of the two resources to be >> related. The value here must also be present as a RESOURCEID in >> the .arches file. >> - START_DATE is a non-required field intended to indicate the date >> at which a given relationship between resources began. >> - END_DATE is a non-required field intended to indicate the date >> at which a given relationship between resources ended. >> - REALTION_TYPE is a domain value driven by an authority document >> file calledARCHES RESOURCE CROSS-REFERENCE RELATIONSHIP >> TYPES.E32.csv. Any value that you put into this column must be a >> conceptid from that authority document. If you wish to customize >> the set of available relationship types, simply modify the >> authority document. >> - NOTES is a non-required field into which additional text about >> the relationship can be captured. >> >> I'd like to seek some clarification: >> >> 1. How should the column headers for "ARCHES RESOURCE CROSS-REFERENCE >> RELATIONSHIP TYPES.E32.csv" look like? >> >> >> 2. Should "ARCHES RESOURCE CROSS-REFERENCE RELATIONSHIP TYPES.E32.csv" >> be located in the "source_data\concepts\authority_files"? >> >> 3. Does each entry in "ARCHES RESOURCE CROSS-REFERENCE RELATIONSHIP >> TYPES.E32.csv" need to be mapped to a domain node via >> "ENTITY_TYPE_X_ADOC.csv"? >> >> 4. Is it accurate to say that, in order to conform to the CIDOC CRM >> ontology, a "relation" (in context of Arches HIP) should be mapped to a >> domain node that is a CIDOC CRM "Property"? >> >> >> Thank you for your time! >> >> Best wishes, >> yikang >> >> > -- -- 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.
