Hello everyone, Thanks for checking this post and providing feedback to my inquiry. Any suggestions would be welcomed! Here is our puzzle:
Here in Nepal, we have been tasked with implementing a comprehensive heritage database. Due to the logistical nature of the region, it would be very beneficial for the heritage information and records to be accessible from one place. Therefore, we are facing 3 main objectives with this comprehensive database: 1. Documenting *Architectural Heritage*, including monuments, caves, stupas, and other built resources. These resources should be tagged geographically, and supported with information resources such as photos, maps, assessments, etc. 2. Documenting the extensive Features/Components of a built resource. This includes murals, sculptures/images, decorative features, and many carved wooden struts, and can be considered as *Collections of Immoveable Objects*. 3. Documenting *Collections of Moveable Objects*, including those of museums and private ownership Arches is ideal for objective #1. But #2 and #3 pose problems. While Arches does record components, from my understanding, it is not meant for *large* amount of components (or "immoveable collections"). For example, if we have a temple with 100 carved wooden struts, all which have been documented/photographed and numbered (because they must exist in sequential order), this collection of components may exceed the "components" section of a resource's report. Similarly with objective #3, the amount of moveable objects in a museum could also overwhelm or clutter a resource's report. Therefore, we have toyed with the possibility of storing the Immoveable/Moveable Collections items separately (in a different inventory), and listing them as External References for respective resources. Thus our main Arches site would have linked branches to other inventories. My question is: Would this branching scheme help us to accomplish our 3 goals without becoming too cumbersome? And if so, does anyone have recommendations for a straightforward museum collection inventory software? Or does anyone have any other recommendations for how to integrate these 3 objectives into one inventory? Let me also note that Nepal's conditions are not always stable. Therefore, the most *user-friendly* and *straightforward* systems would be ideal. Anything too complicated is likely to result in the database not being used. THANK YOU in advance for any feedback! It is greatly appreciated, Allison -- -- 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.
