Haha, time flies indeed :-) The website is looking a hundred times better -
thank you, will pass it on to our developer.
Thanks a million for this, Vincent.
I'm only in the office twice a week, but as soon as I'm back at this I'll
be in touch again (hope you don't mind).
S
On Thursday, 12 September 2019 14:03:18 UTC+2, Vincent Meijer wrote:
>
> That is almost 2 years ago? How time flies!
> Also: congrats on the new website, it looks great.
>
> Some answers:
>
> - Would you advise that I become very familiar with the CDOC CRM
> documentation before I get started? When designing new Resource Types
> in Arches you will definitely need some basic knowledge, as you will need
> to choose a CIDOC type for every field/property that you create. How far
> you want to go depends on your needs regarding CIDOC. If you need to
> publish academic papers about how you implemented your database and abided
> by ontological rules, then you certainly need in-depth knowledge of CIDOC.
> In case of GDH, it is more important to them to release as much data to
> the
> public as possible, than to be very precise and academic about the data,
> especially CIDOC-wise. I encountered many scenarios where I couldn't find
> a
> fitting CIDOC type for a property I was creating. Initially I kept
> dwelling
> on this and it caused major slowdowns and headaches. Now in such a
> situation I generally choose a CIDOC type that 'sounds about right' and
> move on (don't tell the purists!). In any case the Arches community, as
> well as the core team, have CIDOC specialists that can help you.
> - Because we are based at a university, am I correct that it would
> make more sense to install Arches on a server? Arches is an
> 'enterprise level' application, which means your production
> ('live'/public)
> installation will be on a server, running behind a web server. For local
> development and testing: If you want to develop your Arches implementation
> (especially your Resource Types) with multiple people in parallel, then
> installing Arches on a (non-public development)server is the way to go. If
> it is just you, then having a local installation on your laptop can be
> sufficient for developing. However, even though I am currently the only
> developer for GDH, I still like to have a test environment on a server
> outside my laptop, preferably one that is identical to my production
> server. In any case, make sure that your data/work is always backed up
> somehow (I commit everything I do to Github, including my Resource Type
> exports (in .json format)).
> - Our database is in the process of being migrated to the university's
> repository, and I want to make any data of ours on Arches link back to
> those DOIs, so that our website+Arches and our data in the university's
> repository all speak to each other. Does that make sense? This makes
> sense. You can add a free-text field to any Resource Type for copy/pasting
> in the DOIs. Some example Resource Types that ship with Arches already
> have
> something similar (I think it's under 'External References' or similar).
> - We want to make our raw data as well as our visualisations (3D
> models etc) available through Arches. We would need some kind of access
> control, so that viewing models is open to all guests, but access to our
> raw data would need registration. This is possible. You can define
> access on the level of the Resource Type, so for your 3D Model resource
> type you can set it to public, while for your Raw Data resource type you
> limit access to a specific user group (so Raw Data resources will not even
> show up in search results for guest users). Or you could do this only on
> certain properties of a Resource Type (on the 'Cards' level). To do this:
> Go to Arches Designer -> Click a Resource Type -> Click the third tab:
> 'Permissions' -> Click 'Select all' to select all fields ('Cards') of the
> Resource Type (or select only those you want to limit) -> Select a user
> group from the dropdown (use 'anonymous' for public) -> Check the
> appropriate permissions -> Click 'Apply Permissions'
> - Your description of how you envision our data (from your
> conversation with Roshan in 2017) is really useful. Would you change
> anything about it with regard to Zamani’s specific data and updates to
> Arches? I had something like this in mind, but am very open to any
> suggestions and insight: I use the setup as described in that post,
> except I changed a few words and expanded some Types.
> - Instead of 'Activity Resource' I called it '*Project*
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/Project.json>
> '.
> - Instead of 'File (set)' I now use separate Resource Types for
> different file types/formats we have, e.g. '*3D HOP Model
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/3D%20HOP%20Model.json>*',
>
> '*Image
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/Image.json>*'
>
> and '*Video
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/Video.json>*
> '.
> - For raw data I used '*3D Data As Captured
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/3D%20Data%20As%20Captured.json>*'
>
> (Early stages, still working on that).
> - Instead of 'Architectural Resource' I used '*Heritage Site
>
> <https://github.com/globaldigitalheritage/arches-3d/blob/master/arches_3d/arches_3d/db/graphs/resource_models/Heritage%20Site.json>*'
>
> (more or less comprises everything that is not a 'Heritage Object'
> ('portable' stuff)).
>
> I hope this helps. Good luck!
> Vincent
>
--
-- 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/archesproject/e45bfab6-68c8-4ff3-b945-ecaaf1dbf701%40googlegroups.com.
