| | 1 | == Meeting between MPIWG group & eSciDoc team members, 16-17 October, Munich == |
| | 2 | |
| | 3 | MPIWG participants: R. Casties, M. Hyman, W. Schmidle, K. Thoden, J. Willenborg |
| | 4 | |
| | 5 | === eSciDoc architecture as of 2008-10-16 === |
| | 6 | |
| | 7 | * three layers |
| | 8 | * common functionality |
| | 9 | * generalized and unified data model for all content resources |
| | 10 | * content modeling of resources as a specialization instrument |
| | 11 | * versioning |
| | 12 | * PID |
| | 13 | * currently a political problem; to be implemented really for faces etc. by year-end |
| | 14 | * user management, authentication and authorization |
| | 15 | * intermediate services (added functionality) |
| | 16 | * duplicate detection |
| | 17 | * image handling |
| | 18 | * metadata handler |
| | 19 | * validation of data |
| | 20 | * retrieval/download statistics |
| | 21 | * workflow management |
| | 22 | * application services (can be integrated) |
| | 23 | * depositing |
| | 24 | * publishing |
| | 25 | * quality assurance |
| | 26 | * citation manager |
| | 27 | * export manager |
| | 28 | * SearchAndOutput |
| | 29 | * controlled vocabularies |
| | 30 | * use of Fedora |
| | 31 | * Fedora has its own versioning model |
| | 32 | * versioning model is component-level |
| | 33 | * no version numbers (data-based versioning) |
| | 34 | * core services of eSciDoc implement versioning independently |
| | 35 | * an eSciDoc item may be more than one Fedora object |
| | 36 | * three stages |
| | 37 | * pending |
| | 38 | * submitted (some quality control) |
| | 39 | * released (a published, valid object) |
| | 40 | * after release an object cannot be deleted (to ensure persistence) |
| | 41 | * interfaces |
| | 42 | * SOAP and REST |
| | 43 | |
| | 44 | === Overall evaluation === |
