You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
Deployments could benefit from having an optional projectID
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)
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
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.
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).
The text was updated successfully, but these errors were encountered:
@sannegovaert since your task list refers to the implementation in the R package camtrapdp, I have removed your comment here and added it as inbo/camtrapdp#75 (comment)
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:
deploymentID
remains unique)projectID
mediaID
remains unique)observationID
remains unique)scope: media
are listed, it won't be clear which one applies to which media.projectID
to link to the correct project info.The main issue is
project
(and to lesser extendlicenses
). I think supporting multipleprojects
and adding aprojectID
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 pluralprojects
(cf.licenses
,sources
,references
).The text was updated successfully, but these errors were encountered: