In Cidoc CRM there are more classes and properties for rights/Legal Object.
I see three options:
Try to clean Europeana data to fit the needs of Cidoc CRM (as documented here and in this schema from SARI) (The topic of rights seems too important to me to possibly lose data here during the cleaning, since we must not have a loss of data at this point in any case. Even if the data is not really satisfying.)
use edm:rights or dc:rights and include the strings as they are.
use Cidoc CRMs crm:P104 (see below) and put the Europeana String from edm:rights/dc:rights in the E30 class.
E73 Information Object/ E36 Visual Item
crm:P104 is subject to
crm:E30 Right
I think the third way does not lead to 100% clean data, but is maybe the best way to go, especially when we include other CHO data and have the opportunity to model their copyright data in detail.
In Europeana there are the properties edm:rights and dc:rights (they have the same definition). Querying the data from Europeana shows that the entries for dc:rights is heterogeneous and in my opinion not specific enough to model it appropriate in Cidoc. Rights modeling in Cidoc CRM is too differentiated (domain of dc:rights and edm:rights are strings or URIs with heterogeneous information like: "Foto: Köllner, Herbert"; "Verleih: UIP © 2005 Universal Studios."; "FMP"; http://creativecommons.org/licenses/by-nc/3.0/; "Out of copyright. Digital image copyright Jewish Museum, London.").
In Cidoc CRM there are more classes and properties for rights/Legal Object.
I see three options:
I think the third way does not lead to 100% clean data, but is maybe the best way to go, especially when we include other CHO data and have the opportunity to model their copyright data in detail.