Difference between revisions of "User:Natasab/ESciDoc HowTo"

From MPDLMediaWiki
Jump to navigation Jump to search
m
Line 1: Line 1:
==Topics for ESciDoc_HowTO==
==Topics for ESciDoc_HowTO==
===Identify main top-level functions of the solution===
* What are the main functionalities that the solution should fulfill e.g.?
** Create/Edit/Modify/Delete/Search publications
** Create/Edit/Modify/Delete/Search images
** Create Edit/Modify/Delete/Search scanned books
** Create Edit/Modify/Delete/Search digitized manuscripts


===Identify main data entities solution is dealing with===
===Identify main data entities solution is dealing with===
Line 26: Line 18:
**Publications are related to Experiments
**Publications are related to Experiments
**Images of Faces are related to Persons
**Images of Faces are related to Persons
===Identify main top-level functions of the solution===
* What are the main functionalities that the solution should fulfill e.g.?
** Management of publications e.g. Create/Edit/Modify/Delete/Search publications
** Management of images e.g. Create/Edit/Modify/Delete/Search images
** Management of scanned books e.g. Create Edit/Modify/Delete/Search scanned books
** Management of digitized manuscripts e.g. Create Edit/Modify/Delete/Search digitized manuscripts
===Identify main use cases accordingly for each top-level set of functionalities in the solution===
*What shall the management of publications support and who are the actors?
**Management of publications
***Create a publication: depositor
***Update a publication: depositor, moderator
***Approve(release)publication: moderator
***Discard publication: data manager/depositor/moderator
...


===Identify main processes===
===Identify main processes===
*what are the workflows ?
*what are the workflows for each particular entity?
**steps
**steps
**short description
**short description

Revision as of 09:18, 22 September 2012

Topics for ESciDoc_HowTO[edit]

Identify main data entities solution is dealing with[edit]

  • Name the main data entities (short description of what these represent is desirable)
    • Publications
    • Scans of old Manuscripts
    • Scanned Books
    • Images of Faces
    • Simulations
    • Experiments
    • Organizational Units
    • Users
    • Journals
    • Persons
  • Identify how are the main data entities are related (if they are related), try to depict the most important relations e.g.
    • Publications are related to Simulations
    • Publications are related to Experiments
    • Images of Faces are related to Persons

Identify main top-level functions of the solution[edit]

  • What are the main functionalities that the solution should fulfill e.g.?
    • Management of publications e.g. Create/Edit/Modify/Delete/Search publications
    • Management of images e.g. Create/Edit/Modify/Delete/Search images
    • Management of scanned books e.g. Create Edit/Modify/Delete/Search scanned books
    • Management of digitized manuscripts e.g. Create Edit/Modify/Delete/Search digitized manuscripts

Identify main use cases accordingly for each top-level set of functionalities in the solution[edit]

  • What shall the management of publications support and who are the actors?
    • Management of publications
      • Create a publication: depositor
      • Update a publication: depositor, moderator
      • Approve(release)publication: moderator
      • Discard publication: data manager/depositor/moderator

...

Identify main processes[edit]

  • what are the workflows for each particular entity?
    • steps
    • short description

Map to the eSciDoc data model[edit]

  • Identify the object pattern for your main data entities (Item, Container, Organizational Unit, Context)

Define your content model[edit]

  • Select type of resource: Item, Container, Context, Organizational Unit
  • use existing CModel or new one?
  • if new then: which metadata profile for resource, evtl. metadata profile for components