Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Medspiration</strong><br />
MED-SOC-RS-001_1<br />
<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong><br />
Issue F<br />
the external sites within <strong>Medspiration</strong> or GHRSST-PP systems, GHRSST-PP entities,<br />
master metadata repository and error log system.<br />
SR.CTR.0520/I The IFREMER system controller shall also ensure the control and the<br />
sequencing of all the processes run on its own site. Other production sites (CMS, SOC)<br />
shall rely on their own local practices and facilities for the control and the sequencing of<br />
their processes.<br />
3.3.5.8 Exchange MMR<br />
SR.CTR.0530/I A MMR-FR file shall be delivered to the Master Metadata repository for<br />
each L2P and DDS data registered to the archiving system. This will inform the<br />
GHRSST-PP that the related data file is available. No MMR-FR will be generated nor<br />
delivered for the UHR/L4 products.<br />
This restriction comes from the SoW which does not state the GHRSST-PP as a client of<br />
the <strong>Medspiration</strong> UHR/L4 products. Therefore, delivering related MDB records, MMR-FR<br />
or HR-DDS is considered as meaningless in the frame of the GHRSST-PP.<br />
SR.CTR.0540/I Each archiving site (IFREMER for L2P, SOC for HR-DDS) shall be<br />
responsible for generating and sending the MMR-FR files related to the data files it is in<br />
charge of. The MMR-FR shall be delivered to the MMR as soon as they have been<br />
successfully ingested in the archiving system.<br />
3.3.5.9 Exchange error messages<br />
SR.CTR.0550/I The system controller shall format and deliver all specified error<br />
messages to the GHRSST-PP error log (ERRLOG) system.<br />
A tentative list of relevant messages is detailed in GDS Annex 7. This list is likely to<br />
evolve : as <strong>Medspiration</strong> project progresses, error or operation messages of interest will<br />
be submitted to be included or deprecated. The system shall thus be flexible enough to<br />
accommodate new messages.<br />
SR.CTR.0560/I The system controller shall ingest all GHRSST-PP error messages sent<br />
to <strong>Medspiration</strong>. The ingestion of these messages shall be reflected in the operation log<br />
subsystem and in the monitoring subsystem.<br />
No specific action from RDACs is requested by the GDS when receiving an error<br />
message (only one message specified so far : “MDB data rejected from MDB”).<br />
© 2004 SOC Page 56 of 193
Change language