System Requirements Specifications

Actors

• Automatic Trigger
• Event Processor
• UI User
• DMZ User
• Administrator

Use Cases

• Automatic Trigger
  • CCA content publishing
    • Get package from FTP folder
    • Process package
    • Send notification
  • CDSR content Publishing
    • Get package from XFER SFTP folder
    • Process package (unpack validate convert including rendering store)
      • Validation includes naming check image links consistency xml validation and dates in case of update
    • ASAP send packages to subscribers WOL and HW according to package descriptions
    • Cleanup source XFER SFTP folder but not the local data
  • CDSR content update and adding\removing translation
    • reject if content is in waiting state
    • same as publishing (except updates - they do not sent to WOL)
  • CDSR content Scheduled publication
    • same as above but at date specified in metadata
  • CDSR content Scheduled publication cancellation
    • Get SPD- package from XFER SFTP cancelation folder
    • Process package (unpack convert store)
    • ASAP send packages to subscribers HW according to package descriptions
    • Cleanup source XFER SFTP folder but not the local data
  • CDSR content Mesh update for Medhand
  • Editorial content Content Publishing
    • same as CCA CDSR publishing process
  • CENTRAL monthly (last month day) content processing
    • same as publishing
  • MeSH monthly updates processing
    • Accesses PubMed FTP to check mesh updates
    • If updates local images are re-rendered
  • MeSH yearly updates processing
    • Same as monthly but plus possible thesaurus updates
  • Local send packages yearly cleanup
  • Local packages 3-yearly archival
• Event Processor
  • HW publish event processing
    • get publish date from event
    • update content with received dates
    • convert to wiley ml and send package to DS
  • HW cancel event processing
    • delete content which is waiting scheduled delivery
  • WOL acknowledge event
    • publish content to DS
• UI User
  • Publish content
  • Visual content QA including rendering article check
  • Track event history
  • Track user activity
  • Manual triggering of a Publication notification from XDPS to Cochrane.
• External User (from Cochrane for example)
  • Test editorial in stage
    • Put editorial package into wiley-verification folder (on qa/or/sit/prod?) - as a result it is published into HW (Semantico) stage
• Administrator
  • MeSH yearly updates processing
  • Syncronize SIT with Prod database plus local files
  • Application deployment
  • Add someone to prod/qa email notifications
  • Cleanup invalid or failed packages
    • Lookup for status (database)
    • [Optoinal] Cancel process - via UI - if event not received

Data Formats

• XDPS data storage
• Input packages
• Input events
• Notifications

Glossary

References

Appendix Content processing flow