Difference between revisions of "PubMan Func Spec Yearbook of the MPS"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* Users have to be aware of, that the export of PubMan data for the YB to eDoc will be done only once. To avoid duplicates. PubMan ID will be kept as local ID in eDoc and URI to PubMan. | * Users have to be aware of, that the export of PubMan data for the YB to eDoc will be done only once. To avoid duplicates. PubMan ID will be kept as local ID in eDoc and URI to PubMan. | ||
* only PubMan origin items can be added to the yearbook. Imported eDoc data therefore can't be added to the yearbook via PubMan. | * only PubMan origin items can be added to the yearbook. Imported eDoc data therefore can't be added to the yearbook via PubMan. | ||
* PubMan should provide a list of items imported from eDoc, which are members of the YB. Dev. team should be able to provide the difference. | |||
==Yearbook workflow in eDoc== | ==Yearbook workflow in eDoc== | ||
Revision as of 13:50, 17 December 2008
This specification describes how the yearbook of the MPS will be handled as long as eDoc is still used for the creation of the yearbook, while the rest is handled within PubMan. The idea is, that eDoc should only be used to release the data exported from PubMan for the yearbook of the MPS.
Yearbook workflow in PubMan[edit]
- There will be one container (folder) for the yearbook records in PubMan (per institute)
- Who will be able to create that container? Me via the admin interface? --Nicole 12:35, 1 December 2008 (UTC)
- Container(s) will be created by Dev. Team manually.
- A container only holds the links to items.
- Containers will have MD on the responsible institute (OU) via the context.
- Who will be able to create that container? Me via the admin interface? --Nicole 12:35, 1 December 2008 (UTC)
- (released) records can be added to that yearbook container from the qa workspace or from view item version.
- Who should be able to recommend items for the yb container? Only moderator or also depositor? --Nicole 12:35, 1 December 2008 (UTC)
- For now only the moderator.
- Who should be able to recommend items for the yb container? Only moderator or also depositor? --Nicole 12:35, 1 December 2008 (UTC)
- items, which are in the yearbook container will be marked as recommended for the yearbook
- the content of the container can be viewed and edited by moderators.
- How will the moderator be able to view the items in a container? From his workspace? --Nicole 12:35, 1 December 2008 (UTC)
- Will be part of the QA workspace.
- How will the moderator be able to view the items in a container? From his workspace? --Nicole 12:35, 1 December 2008 (UTC)
- Container will be released when it is ready for the export to eDoc (will be done by the moderator). Items in the container will then be marked as released for yearbook YYYY. Once the container has been released no further records can be added or removed.
- PubMan export will be done.
- Users have to be aware of, that the export of PubMan data for the YB to eDoc will be done only once. To avoid duplicates. PubMan ID will be kept as local ID in eDoc and URI to PubMan.
- only PubMan origin items can be added to the yearbook. Imported eDoc data therefore can't be added to the yearbook via PubMan.
- PubMan should provide a list of items imported from eDoc, which are members of the YB. Dev. team should be able to provide the difference.
Yearbook workflow in eDoc[edit]
- users, that have moved their data to PubMan will only have one collection in eDoc for the yearbook, which will be named "Yearbook YYYY"
- data from PubMan will be imported to eDoc in a virtual collection. Then they have to be copied into a "real" collection (working or archival collection, working is recommended).
- Then they can be all recommended for the yearbook of the MPS and then released for the yearbook. If data is changed in eDoc, it also has to be changed in PubMan manually