Difference between revisions of "ESciDoc Item List"
Jump to navigation
Jump to search
(New page: Idea: 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. Boundarie...) |
|||
| Line 1: | Line 1: | ||
This page is the result of the [Escidoc workshop| eSciDoc workshop in September 2007] | |||
Idea: 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. | Idea: 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. | ||
Boundaries for prototype: | Boundaries for prototype by FIZ: | ||
* with AA | * with AA | ||
* without paging | * without paging | ||
* | * list format RSS in RDF | ||
Requirements (delivered by MPDL): | |||
* item list should be sortable by: | |||
** list hier | |||
Questions: | Questions: | ||
* How to version the changes required if the transformation is | |||
* Is it required to "break" DC rules to create the information required to display item lists? | |||
** If yes: Change of functional specification? | |||
Required: | Required: | ||
* Transformation mechanism | * Transformation mechanism | ||
* Versioning mechanism: change in transformation requires change of all items of a specific | * Versioning mechanism: change in transformation requires change of all items of a specific | ||
Revision as of 10:44, 25 September 2007
This page is the result of the [Escidoc workshop| eSciDoc workshop in September 2007]
Idea: 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.
Boundaries for prototype by FIZ:
- with AA
- without paging
- list format RSS in RDF
Requirements (delivered by MPDL):
- item list should be sortable by:
- list hier
Questions:
- How to version the changes required if the transformation is
- Is it required to "break" DC rules to create the information required to display item lists?
- If yes: Change of functional specification?
Required:
- Transformation mechanism
- Versioning mechanism: change in transformation requires change of all items of a specific