Version 1 (modified by 16 years ago) (diff) | ,
---|
Meeting between MPIWG group & eSciDoc team members, 16-17 October, Munich
MPIWG participants: R. Casties, M. Hyman, W. Schmidle, K. Thoden, J. Willenborg
eSciDoc architecture as of 2008-10-16
- three layers
- common functionality
- generalized and unified data model for all content resources
- content modeling of resources as a specialization instrument
- versioning
- PID
- currently a political problem; to be implemented really for faces etc. by year-end
- user management, authentication and authorization
- intermediate services (added functionality)
- duplicate detection
- image handling
- metadata handler
- validation of data
- retrieval/download statistics
- workflow management
- application services (can be integrated)
- depositing
- publishing
- quality assurance
- citation manager
- export manager
- SearchAndOutput?
- controlled vocabularies
- common functionality
- use of Fedora
- Fedora has its own versioning model
- versioning model is component-level
- no version numbers (data-based versioning)
- core services of eSciDoc implement versioning independently
- an eSciDoc item may be more than one Fedora object
- three stages
- pending
- submitted (some quality control)
- released (a published, valid object)
- after release an object cannot be deleted (to ensure persistence)
- interfaces
- SOAP and REST