search

archesproject / ARM_Working_Group

Arches Resource Model Working Group. A repo for community reviewed Arches branches, models, and packages
2 stars 2 forks source link

Branch: Production #19

Open annabelleee opened 6 years ago

annabelleee commented 6 years ago

production_20180510

Branch for Production as discussed during May 2018 meetings. JSON pending.

Steps to completion (updated):

azaroth42 commented 6 years ago

Production model: production_model

The only difference is our need for influenced_by for copies of works (which can be ignored for a simpler model ... but I don't know if that's what I would take out first, we should look to the instance data for that)

Habennin commented 6 years ago

I represented this also in the google sheet to capture the particular properties and paths of CRM.

https://docs.google.com/spreadsheets/d/1EYk1yhhBNWrKbVB0jV_1j8NJ-Egi5zWha7QrVvYvw3s/edit?usp=sharing

I think the two representations are the same.

As a matter of method, we can see that the production only specializes the E7 Activity branch, adding more potential information. Could there be a way to create inheritance between branches so that an upper branch would pass its defined properties to a sub branch?

I also don't know, but market in the google sheet, what happen in Arches when you poni to a general class like E1 (as CRM lets you do for P15i influenced by). Are you able to specify multiple branches that could satisfy that property or only one? In which case would you have to make a bunch of odiffernet properties for the branch like 'Influnced by Person' 'Influenced by Event' 'Influenced by Idea' and so on?

annabelleee commented 5 years ago

metadata and sample data: https://docs.google.com/spreadsheets/d/1KV2hEfTur6Lc2LEhCc-vzcKioUTAoY1gnjxjCQXiB_o/edit#gid=6050444