Hello Joel, The graphs that come default with v4 are here: https://github.com/archesproject/arches/tree/master/arches/db/graphs/resource_models
Is that what you were looking for? Best, Vincent On Sunday, 30 April 2017 04:06:35 UTC-4, Joel Aldor wrote: > > Hi Dennis, > > I'm done with Step 1 of the migration. For Step 2, we wish to retain first > the default HIP graphs we had for version 3, before we make any changes to > our data models using the Arches Designer. Could you provide us the updated > graphs for version 4? > > Thank you, > > Joel > > On Friday, April 7, 2017 at 3:20:47 AM UTC+8, Dennis Wuthrich wrote: >> >> Migrating from v3 to v4 >> >> We've heard from a few people, asking about migrating from Arches v3 to >> v4. To help you understand the basic approach, we've outlined the workflow >> as a series of steps: >> >> Step 1. Export your RDM/Reference data from v3 >> Step 2. Create graphs in v4 >> Step 3. Migrate business data from v3 to v4 >> >> Of course, the devil is in the details! >> >> *Step 1: Export RDM data from v3.* >> We're working on a patch that will allow you to use the RDM SKOS exporter >> (Tools -> Export Scheme) to export your existing RDM from v3 into a format >> that v4 can read. Once you've exported your existing concepts, use the v4 >> RDM to import them. >> >> We've introduced a new feature in v4 called "collections" that allow you >> to manage dropdowns in data entry forms in a manner that adhers to the skos >> standard. You'll need to use the RDM to create collections for your >> dropdowns. >> >> >> *Step 2: Create graphs in v4* >> In v4, Arches provides a way to create and validate graphs interactively. >> The "Arches Designer" in v4 offers visual graph creation tools that you'll >> need to use to create graphs. >> >> If you're using the default HIP graphs in v3, this step is pretty easy as >> we'll provide updated versions for v4. If you've created your own graphs >> (or modified the existing v3 HIP graphs), you'll need to use the Arches >> Desiger to create your graphs in v4. >> >> In either case, migrating from v3 to v4 is a chance for you to >> re-evaluate your data models and implement improvements based on your >> experience with v3. You'll find that v4 comes with a library of re-usable >> "branches" (or sub-graphs) that make designer a graph much easier than for >> v3. >> >> One last note: v4 validates graphs to ensure that they are consistent >> with the CIDOC CRM classes and properties. This means that graphs in v4 >> need to be semantically valid (NOT a requirement of v3). >> >> >> *Step 3: Migrate business data from v3 to v4* >> After configuring the RDM and defining graphs in v4, you're ready to >> import your v3 data. >> >> To start, export data from your v3 instance of Arches. V3 comes with a >> command that will export your business data to JSON. You'll need to use a >> JSON to csv converter (or write a script to do it), then use v4's CSV >> import tools to pull your data into Arches. V4 comes with mapping tools >> that allow you to map information in a CSV file to specific nodes in a >> resource model. >> >> Of course, there are always lots of details when working with a specific >> dataset. But the basic process can be broken down to the 3 steps outlined. >> >> We at Farallon will be supporting v3 to v4 migrations, but there's no >> reason you can't do it yourself. >> >> Hope this helps... >> >> Cheers, >> >> Dennis >> > -- -- 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.
