Difference between revisions of "ESciDoc Item List"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
Base filter methods on a "mini item" = a specific data stream with minimal metadata. the metadata would be created "content type" specific with creation/update of an item. | Base filter methods on a "mini item" = a specific data stream with minimal metadata. the metadata would be created "content type" specific with creation/update of an item. | ||
[[Image: | [[Image:Sketch_razum1.jpg]] | ||
== Prototype == | == Prototype == | ||
Revision as of 13:00, 25 September 2007
This page is the result of the eSciDoc workshop hold in September 2007. It should serve for collecting of ideas, questions & constraints discovered while evaluating the filtering of items according to a "mini item" information object. Please feel free to use the page ;)
Basic Idea[edit]
Base filter methods on a "mini item" = a specific data stream with minimal metadata. the metadata would be created "content type" specific with creation/update of an item.
Prototype[edit]
Boundaries for prototype by FIZ:
- with AA
- without paging
- list format RSS in RDF
Requirements (delivered by MPDL):
- item list should be sortable by:
- item list currently include following metadata:
- list hier
- transformation rules are available:
Questions & Discussion[edit]
- How to version the changes required if a change in the transformation requires a change of all item of a specific content type
- Is it required to "break" DC rules to create the information required to display item lists?
- If yes: Change of functional specification?
- Should a change of the "mini item" data stream
- create a new logical version?
- create no new logical version?