search

cessda / cessda.metadata.profiles

Contains DDI Profiles that are used by the CESSDA Metadata Validator Tool
Other
0 stars 0 forks source link

Profiles vs CMM: Clarify purpose of each. #101

Open cessda-bitbucket-importer opened 2 years ago

cessda-bitbucket-importer commented 2 years ago

Original report on BitBucket by Darren Bell (GitHub: darrenbell2).

From Olof Olsson 01-Nov-21. Basecamp Message ID: https://3.basecamp.com/3584575/buckets/1716357/messages/4282415300#__recording_4306736571

General feedback:
It would be easier to maintain and implement a single profile for both CMM and EQB, there is a huge overlap.
I would expect EQB to be additional requirement of the same source as CMM.
It would be hard to build and validate separate output for CMM/EQB.

cessda-bitbucket-importer commented 2 years ago

Original comment by Darren Bell (GitHub: darrenbell2).

Not the first time this issue has been raised. As the profiles mature and the number of profiles increases, it becomes a challenge to keep all of these artefacts in alignment at both a human and a machine-actionable level. It is worth considering and re-iterating what distinct purpose the CMM serves, beyond what the profiles offer.