Why does every US Government agency need a different one of these?

[dmlb2000]

I'm just wondering why every government agency needs to have a different one of these...

• https://github.com/pacifica/pacifica (the one I work on)
• https://github.com/ckan/ckan (other gov agencies)
  • https://github.com/GSA/data.gov/ (with some word press?)
• https://github.com/GetDKAN/dkan2 (Drupal CKAN)
• https://github.com/nasa/data-nasa-gov-frontpage (It'd be nice to know what's behind this)
• https://github.com/doecode/doecode (code repo but holds data too)
• There's more NIH has a bunch
• https://github.com/ARM-DOE/

It'd be nice to have a standard way government can build a data repository, so we can all use the same technology in the same way.

[GRG2]

Thank you for the comment. Our team completely appreciates this perspective.

Your question highlights further documentation may be helpful as a basis for this implementation. A thorough trade study was conducted to evaluate trusted repository solutions. This implementation has prioritized standards for Research Data publication, long term digital object preservation and interoperability in balance with NIST infrastructure requirements (i.e. data workflow/processes, organizational taxonomy, and integration with policy review).

In support of the NIST mission, we are working with the Research Data community in development of a framework which extends beyond user interfaces and single platform solutions. This ideally will be a shared resource to inform Research Data organizations, including government agencies which operate in this space, best practices and standards for data management, curation, public data access and dissemination.

[dmlb2000]

Sorry, but I'm going to start picking apart your statements.

From your first paragraph, please correct me if I'm wrong. This data repository is NIST's research data repository and not a standard repository for others to consume? As the implementation has been balanced with (not separated from) NIST's infrastructure requirements?

I really want to have a community lead standards compliant implementation to support Research Data publication, long term digital object preservation and interoperability with documentation on how I can implement the system for my institution. So, please let me know when you plan to separate the common Research Data repository requirements from the NIST infrastructure requirements.

I agree that documentation and discussion would be helpful on this topic. I would really like to see the US Gov create a common platform to create Research Data repositories. It is going to be very hard to achieve interoperability and reuse (FAIR principles) without common components driving all our implementations.

Just my thoughts.

[GRG2]

Your feedback and comments are WELCOME.

Correct read, this repository software is being shared for collaboration and as a reference for standards implementation for data publication and to serve the NIST community. It is not being promoting as a brand of repository. There are a couple related publications that we will add linked documentation to that may be helpful.

Responding to the specific comment:

"I really want to have a community lead standards compliant implementation to support Research Data publication, long term digital object preservation and interoperability with documentation on how I can implement the system for my institution."

This is widely recognized. As mentioned in the earlier reply, NIST is partnering with other leaders in the research data community toward development of a research data framework. Documentation should be forthcoming to describe the efforts, it is still in early stage of activity.

Establishing a suite of shared tools and services is something we are working toward...the Core Trust Seal audit is underway for this repository system.