Thank you very much indeed Adam. Having all the steps laid out in this way is very helpful. I think step 3 may have been omitted before. I shall ensure that this procedure is passed on.
Lucy Sent from my iPad > On 10 May 2016, at 16:10, Adam Cox <[email protected]> wrote: > > Hi Lucy, you should have no problem doing this, though to be clear, you'll > have to reinstall the package for the resource graph and ENTITY_X_ADOC > changes to be reflected. Here are the steps you need to be sure to take: > > 1. Modify resource graph: > All CIDOC CRM considerations aside, when it comes to the resource graph > all you need is a node whose business table name is "domains", and for good > measure (though technically it's unnecessary in the graph) you should connect > the E32 authority file to this node. I'm sure you're familiar with this > construction. From what you're describing, it sounds like you can just > connect an E32 node directly to the E48, and then change the E48 business > table from strings to domains. > 2. Fix up the ENTITY_X_ADOC file > Sounds like you have done this, but the rule here is very simple: Any > "domain" nodes in the graph that are connected to an E32 authority file node > must be listed here in column one, and column two has the file name of the > authority document. ENTITY_X_ADOC is actually the only thing that Arches > uses to pull the authority files into the RDM (not the E32 nodes in the > resource graphs) and link it to the domain nodes. > 3. In your Location form in forms.py file, you'll now need to add the E48 > node as a domain in the E48 branch-list, like this: > <image.png> > 4. You shouldn't have to change anything in your location.js file. > 5. In your location.htm file, you'll now need to use a select2 widget to > replace the manual entry input for the E48 node. Just copy and paste the > admin type input, and change the node name. Finally, in the block that > appears below the input showing what has already been added, you'll need to > make sure that the E48 node label is referenced, not the value. > > Hope all of that makes sense. You probably are just missing one little > detail somewhere. > Adam > > >> On Tue, May 10, 2016 at 5:58 AM, 'Lucy Fletcher-Jones' via Arches Project >> <[email protected]> wrote: >> Hi Phil, >> >> Thank you for your reply. You had told me this before and that is what I >> specified for the programmer but it is technically non standard and my >> programmer found it didn't work, but it must have been because of a bug. >> Thank you for pointing me to E57 Material as an example, we are not going to >> this level of detail so did not look at this. I will ensure our next >> programming resource does it this way unless anyone else has found it does >> not work on a technical level? >> >> Lucy Fletcher-Jones >> Egypt Database Project >> TMP Room 2181, HUSS Building AUC New Campus >> Tel: 02 2615 1760 >> Mobile: 010 1633 8367 >> >> >>> On Tue, May 10, 2016 at 12:35 PM, Carlisle, Philip >>> <[email protected]> wrote: >>> Hi Lucy, >>> >>> There should be no problem with you modifying the graph to do this. In the >>> CRM E48 Place Name specifically states that instances of E48 are usually >>> subject to a gazetteer (E32). The property P71 is valid for a domain of >>> E32 and a range of E1 (ie. any CRM entity). >>> >>> >>> >>> So instead of E48 P2 E55 –P71 E32 you can cut out the middle man and just >>> have E48 -P71 E32. >>> >>> >>> >>> In essence the E48 Administrative Subdivision is the dropdown (in the dame >>> way E57 Material is the dropdown) >>> >>> >>> >>> I hope this helps >>> >>> >>> >>> Phil >>> >>> >>> >>> Phil Carlisle >>> >>> Data Standards Supervisor >>> >>> Data Standards Unit, >>> >>> Listing Information Services >>> >>> Listing Group >>> >>> Historic England >>> >>> The Engine House >>> >>> Fire Fly Avenue >>> >>> Swindon >>> >>> SN2 2EH >>> >>> Tel: +44 (0)1793 414824 >>> >>> >>> >>> http://thesaurus.historicengland.org.uk/ >>> >>> http://www.heritagedata.org/blog/ >>> >>> >>> >>> Listing Information Services fosters an environment where colleagues are >>> valued for their skills and knowledge, and where communication, customer >>> focus and working in partnership are at the heart of everything we do. >>> >>> >>> >>> From: 'Lucy FJ' via Arches Project [mailto:[email protected]] >>> Sent: 10 May 2016 11:22 >>> To: Arches Project >>> Subject: [Arches] Adding domains to a 'name' entity >>> >>> >>> >>> Hi all, >>> >>> >>> >>> We are experiencing some programming difficulty with a customization, that >>> I thought would be easy. We wish to add a domain, a drop down list to >>> ADMINISTRATIVE_SUBDIVISION.E48 instead of allowing the user to input a free >>> form name. The .E48 is linked with ADMINISTRATIVE_SUBDIVISION_TYPE.E55. We >>> would only have one value in this subtypes authority file. In the >>> ENTITY_X-ADOC file the .E48 would be linked with the .E32 authority >>> document. In theory is it possible to do this? We realize we cannot add any >>> more >>> >>> >>> >>> We tried this but it did not appear to work (but could have been simply >>> some programming bugs) so we created a new type.E55 node and update that >>> node instead. However for various reasons this is not working and it does >>> mean that the .E48 node is not being updated at all. I would prefer to go >>> back to our first idea but will it work? It is not a standard Arches way of >>> proceeding. >>> >>> >>> >>> Thank you for any help, >>> >>> 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 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. >>> >>> >>> >>> We are the public body that looks after England's historic environment. We >>> champion historic places, helping people to understand, value and care for >>> them, now and for the future. >>> Sign up to our enewsletter to keep up to date with our latest news, advice >>> and listings. >>> >>> HistoricEngland.org.uk Twitter: @HistoricEngland >>> >>> This e-mail (and any attachments) is confidential and may contain personal >>> views which are not the views of Historic England unless specifically >>> stated. If you have received it in error, please delete it from your system >>> and notify the sender immediately. Do not use, copy or disclose the >>> information in any way nor act in reliance on it. Any information sent to >>> Historic England may become publicly available. >>> >>> >> >> -- >> -- 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.
