[Moims-dai] [EXTERNAL] Reminder of Skype call today

Hughes, John S (398B) john.s.hughes at jpl.nasa.gov
Tue Apr 30 13:38:54 UTC 2019 

Hi all,
Sorry I will not be able to attend. The Insight mission has a looming deadline and I have a couple of action items.
Steve

Sent from my iPhone

On Apr 30, 2019, at 4:43 AM, David Giaretta <david at giaretta.org<mailto:david at giaretta.org>> wrote:


Meeting: 10:00 Tuesday (EST), 1500 UK time, 1600 European time



Join it by clicking the link:

https://join.skype.com/ykyu5SIPhSnD



*Don't have Skype yet? Download it before you join https://www.skype.com



General schedule:

Tuesday of the month

Activity

Technical Editor(s)


1st

ISO 16363    Audit and Certification Metrics

John Garrett, David Giaretta


2nd


IPELTU Info Preservation Enabling Long-Term Usage


David Giaretta


3rd


OAIS-IF DAADD    OAIS Interoperability Framework – Digital Archive Architecture Design Doc


Steve Hughes


4th


OAIS-IF and reports on OAIS update finalization, Group administration, Planning, new projects, or special issues identified other weeks





5th


OAIS-IF and reports on OAIS update finalization, Group administration, Planning, new projects, or special issues identified other weeks




Draft agenda this week (5th Tuesday of the month):

  1.  Brief report on status of OAIS v3 draft – I made my last, minor, edits to OAIS – marked in the comments with “20190425”. Also added a summary of changes to the document history. The following link is to the Word file which has all comments including references to review.oais.info<http://review.oais.info>:  https://cwe.ccsds.org/moims/docs/MOIMS-DAI/OAIS-related/OAIS-v3/OAIS%20final%20v3%20draft%20with%20changes%20wrt%20OAISv2%2020190425.docx?Web=1


A PDF with simple mark-up is at:

https://cwe.ccsds.org/moims/docs/MOIMS-DAI/OAIS-related/OAIS-v3/OAIS%20final%20v3%20draft%20with%20changes%20wrt%20OAISv2%2020190425.pdf.

              I plan to send docs to MOIMS AD immediately after the meeting.

  1.  Preparation for CCSDS plenary
  2.  OAIS-IF status
  3.  IPELTU status
  4.  RASIM status
  5.  ISO16363 review
Suggested Change ID

Product

Component

Summary

Explanation of the reason for the suggested change

Reporter

Category of change

44

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Identifiers - Submetrics (4.2.4.1.x) – Can the five metrics be combined?

These submetrics seem to be much more detailed than most submetrics.

steve.hughes at jpl.nasa.gov<mailto:steve.hughes at jpl.nasa.gov>

Recommended change for other considerations

45

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

Identifying and managing risks - Submetrics (5.1.1.1.x) - Can the eight metrics be reduced to two?

These submetrics seem to be much more detailed than most submetrics.

steve.hughes at jpl.nasa.gov<mailto:steve.hughes at jpl.nasa.gov>

Recommended change for other considerations

48

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Align the ISO 16363 metrics more closely with the Mandatory Responsibilities

The second mandatory responsibility, “Obtain sufficient control of the information”, is mentioned twice in the metrics, as the focus of metric 4.1.6 and as supporting text for metric 3.5.1.1. However an assessment of the metrics found that this responsibility had the second highest number of supporting metrics. Is there some way to make this fact more clear and to align the ISO 16363 metrics more closely with the Mandatory Responsibilities described on the OAIS Framework? [1]



[1] Hughes, JS, Downs RR. 2016. Criteria for Assessing Repository Trustworthiness: An Assessment. SciataCon 2016, Denver, CO 11-13 September 2016.  http://www.scidatacon.org/2016/sessions/100/paper/36/

steve.hughes at jpl.nasa.gov<mailto:steve.hughes at jpl.nasa.gov>

Updates to add missing concepts or strengthen weak concepts

49

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Revise or update language in metrics  to reflect current capabilities and recent improvements

Generally, revise or update language in metrics, including explanation, discussion, and examples for selected metrics to reflect current capabilities and recent improvements in data management practices, including any revisions that will be made to the Mandatory Responsibilities and other areas described within the CCSDS OAIS Framework, the CCSDS DAI draft on Information Preparation for Long-Term Use, practices recommended in the Group on Earth Observations’ Data Management Principles and Implementation Guidelines, recommendations in the Research Data Alliance’s Data Management Trends, Principles and Components – What Needs to be Done Next?, the Global Climate Observing System’s current revisions to the Implementation Plan for the Global Observing System for Climate in Support of the UNFCCC, Common Framework for Earth Observation Data, DSA–WDS Core Certification and its Catalogue of Common Requirements, FAIR Principles, and the Belmont Forum E­Infrastructure and Data Management: Implementation Plan. [1]



[1] Hughes, JS, Downs RR. 2016. Criteria for Assessing Repository Trustworthiness: An Assessment. SciataCon 2016, Denver, CO 11-13 September 2016.  http://www.scidatacon.org/2016/sessions/100/paper/36/

steve.hughes at jpl.nasa.gov<mailto:steve.hughes at jpl.nasa.gov>

Identification of any outdated material

119

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Changes to ensure updated ISO 16363 is consistent with updated OAIS

This is a catch-all comment to ensure that this standard is consistent with OAIS (ISO 14721).

david at giaretta.org<mailto:david at giaretta.org>

Recommended change for other considerations

244

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.1.2.1 Questions to address

These questions may arise in some audits

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

245

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.1.2.2 Questions to address

Questions that could arise in some audits.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

246

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.2.1.3 Add to Examples of Evidence

Provides additional examples of how to meet criteria

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

247

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.3.1 and 3.3.2 Address issue of "general public" as part of Designated Community

Many archives have general public as customers, but there can be problems if they are included in Designated Community.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

248

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.3.2.1 Add discussion of staff needs

Staff knowledge is an important element for adopting and enforcing policies.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

249

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.3.4 Transparency vs. other needs

For many criteria, there is often not a single concern, but there is a need for balance between competing requirements.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

250

Audit and Certification of Trustworthy Digital Repositories

Section 3  : Organisational Infrastructure

3.5.1 and 3.5.1.1 Add evidence of legislation as example of way to meet criteria

Many archives preserve data because they are legally required to do so.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

251

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

5.1.1 Delete unmatched closing paren

Editorial

garrett at his.com<mailto:garrett at his.com>

Editorial

252

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

5.1.1 Scaling largest systems will likely result in major disruptions

Ensure we are clear what is required and how it relates to determining risks.

garrett at his.com<mailto:garrett at his.com>

Updates to add missing concepts or strengthen weak concepts

253

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

How do 5.1.1.1.2 and 5.1.1.1.3 differ?

Seems to be a lot of overlap.  Not sure criteria are properly stated.

garrett at his.com<mailto:garrett at his.com>

Updates to add missing concepts or strengthen weak concepts

254

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

5.1.1.1.4 Seems to require blank check for hardware updates

Blank checks for updates are not feasible.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

255

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

How do 5.1.1.1.6 and 5.1.1.1.7 differ?

Perhaps these should be collapsed or perhaps rewritten to more clearly indicate the distinct focus.

garrett at his.com<mailto:garrett at his.com>

Updates to add missing concepts or strengthen weak concepts

256

Audit and Certification of Trustworthy Digital Repositories

Section 5  : Infrastructure and security risk management

5.1.1.1.8 Seems to require blank check for software updates

Unrealistic to expect committed funding for any future software updates.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

257

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Add sub-metrics to 4.2.3

Seems like several sub-metrics could be added.  If not, then

metric and sub-metric could be combined.

garrett at his.com<mailto:garrett at his.com>

Updates to add missing concepts or strengthen weak concepts

258

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Restate 4.2.1 criteria

Simplifies criteria.

By definition all AIPs are to be preserved by the repository, so we don't need to include that in the criteria.

garrett at his.com<mailto:garrett at his.com>

Editorial

259

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

4.2.1 Definition of AIP does not help to find the AIP

Definition of AIP does not help to find the AIP

garrett at his.com<mailto:garrett at his.com>

Corrections to matters of fact

260

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

Switch 4.2.1.1 and 4.2.1.2

Makes more sense to talk about the AIP description before saying that an AIP needs to be linked to that description

garrett at his.com<mailto:garrett at his.com>

Editorial

261

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

4.2.1.2 Allow descriptions for class of AIPs

The same definition should be adequate for a whole class of AIPs.

The definition should deal with all components of that AIP whether they are required components or not.

garrett at his.com<mailto:garrett at his.com>

Updates needed for clarification

262

Audit and Certification of Trustworthy Digital Repositories

Section 4  : Digital Object Management

4.2.1.2 Rewrite Supporting Text

AIP descriptions do not alone provide all the services (or possibly any of the services) mentioned in the supporting text.

garrett at his.com<mailto:garrett at his.com>

Corrections to matters of fact




Regards

..David






_______________________________________________
MOIMS-DAI mailing list
MOIMS-DAI at mailman.ccsds.org<mailto:MOIMS-DAI at mailman.ccsds.org>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/moims-dai
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20190430/aea0da8f/attachment-0001.html>

More information about the MOIMS-DAI mailing list