Support combining Camtrap DP into one, i.e. support multiple projects

[peterdesmet]

A use case that comes up quite often is that researchers want to combine Camtrap DP into one Camtrap DP to do a meta analysis. Software could support this and the result would be:

• Deployments: combination of deployments (but check that deploymentID remains unique)
• Media: combination of media (but check that mediaID remains unique)
• Observations: combination of media (but check that observationID remains unique)
• name: a new name is created (old values are not retained)
• id: a new ID is created. The original ids are stored in relatedIdentifiers
• created: reset to current timestamp (old values are not retained)
• title: a new title (old values are not retained)
• contributors: a combination is made, duplicates (on some or all fields) are removed and roles are combined (in Frictionless v2). The order is not retained.
• description: a new one is generated, potentially still listing the previous descriptions
• version: is reset to 1.0 (old values are not retained)
• keywords: a combination is made, duplicates are removed
• image: is removed (old values are not retained)
• homepage: is removed (old values are not retained)
• sources: a combination is made, duplicates are removed
• licenses: a combination is made, duplicates are removed. If e.g. two different license with scope: media are listed, it won't be clear which one applies to which media.
• bibliographicCitation: is removed (old values are not retained)
• project: ideally this becomes an array of projects and deployments have a projectID to link to the correct project info.
• coordinatePrecision: is reset to least precise precision (old values are not retained)
• spatial: is reset based on new deployments (old values are not retained)
• temporal: is reset based on new deployments (old vales are not retained)
• taxonomic: a combination is made, duplicates are removed.
• relatedIdentifiers: a combination is made, duplicates are removed
• references: a combination is made, duplicates are removed

The main issue is project (and to lesser extend licenses). I think supporting multiple projects and adding a projectID to deployments would be the way forward. Software that only supports one project can either populate just one or read only the first one. For consistency, I would rename to plural projects (cf. licenses, sources, references).

[peterdesmet]

@sannegovaert since your task list refers to the implementation in the R package camtrapdp, I have removed your comment here and added it as https://github.com/inbo/camtrapdp/issues/75#issuecomment-2265484138