Changes between Version 5 and Version 6 of CMDI 1.2/Header/MdType


Ignore:
Timestamp:
02/10/14 08:35:35 (10 years ago)
Author:
herold
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Header/MdType

    v5 v6  
    1717
    1818[[mwindhouwer|Menzo]] Using the relations we could distinguish three levels: roots, inner nodes and leafs. It might be problematic to automatically mark all roots and inner nodes as collections. The solutions below would allow each center to determine which are the appropriate ones.
     19
     20[[herold|Axel]]: Maybe we should think about whether it is more helpful for _the users_ to either know that some resource is part of a bigger collection or else how the data provider likes to describe/view the resource. Florian seems to be a proponent of the user's view and I tend to agree. @Menzo, under this view, appropriateness of the part/collection distinction would have to be judged in the light of the user's research question rather than the centre's general decision.
    1921
    2022== Proposed solutions ==
    … …  
    9698==== Discussion ====
    9799
    98 Discuss this solution proposal in this section
     100[[herold|Axel]]: If we include life-cycle management in CMDI 1.2 any changes to such a component would lead to many profiles using a then deprecated module. Also, much of the metadata that you would want to include here already appears in other components so this could easily lead to duplicated information and would generally bloat the profiles.
    99101
    100102=== Fourth solution: the profile root uses a data category from a collection relation set ===
    … …  
    122124==== Discussion ====
    123125
    124 Discuss this solution proposal in this section
     126[[herold|Axel]]: This would be backwards compatible with CMDI 1.1 and generally that's a plus. Considering Florian's point raised at the top of this page this could be seen as a supplement to the resource relation modelling. Using a suitable DatCat for the profile root could encode the data provider's classification of the resource. Another nice aspect of this solution is that we wouldn't have to introduce yet another version of CMDI once we find that a fixed set of Header/MdType values should better be extended.
    125127
    126128=== Fifth solution: collection level instances are harvested from a specific OAI-PMH set ===