PDE-CS Planetary-Data-Ecosystem issues

PDE-CS / Planetary-Data-Ecosystem

Planetary Data Ecosystem Issue Tracking and Discussions

Creative Commons Zero v1.0 Universal

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Recommendation 65: NASA should encourage continuing education of members of the planetary science community

#65 PDE-CS opened 2 years ago
0
Recommendation 64: NASA should seek to expand opportunities for intermediate to advanced technical training...

#64 PDE-CS opened 2 years ago
0
Recommendation 63: The Planetary Science Division should adopt a single, coherent, open source software policy that applies across all its activities.

#63 PDE-CS opened 2 years ago
0
Recommendation 62: Recognizing that “Software is data, but data is not software” ...

#62 PDE-CS opened 2 years ago
0
Recommendation 61: NASA should consider ... filling certain critical Planetary Data Ecosystem software tool needs.

#61 PDE-CS opened 2 years ago
0
Recommendation 60: NASA should consider providing options for funding software tools ...

#60 PDE-CS opened 2 years ago
0
Recommendation 59: NASA should establish a mechanism to support the preservation, support, and maintenance of software tools...

#59 PDE-CS opened 2 years ago
0
Recommendation 58: NASA should increase the level of funding available to explicitly support software development...

#58 PDE-CS opened 2 years ago
0
Recommendation 57: NASA should also consider how the relatively nascent planetary ML/AI/AA user community might not be well-aligned with traditional missions...

#57 PDE-CS opened 2 years ago
1
Recommendation 56: As they proceed with developing the Planetary Data Ecosystem, NASA should ensure that any Ecosystem assessment group considers the needs of current and potential ML/AI/AA users as part of their work.

#56 PDE-CS opened 2 years ago
0
Recommendation 55: NASA should expand public participation in scientific research and other crowdsourcing methods as one strategy for providing data labeling essential to ML/AI/AA.

#55 PDE-CS opened 2 years ago
1
Recommendation 54: NASA should find ways that the Ecosystem could include developer advocacy, particularly for the core PDS application program interfaces (APIs).

#54 PDE-CS opened 2 years ago
0
Recommendation 53: NASA and the PDE should ensure that data linkage mechanisms and types are clearly documented with examples.

#53 PDE-CS opened 2 years ago
0
Recommendation 52: Relevant elements of the Ecosystem should support the delivery of higher-level and analysis-ready data products in well-documented and broadly used protocols and formats...

#52 PDE-CS opened 2 years ago
1
Recommendation 51: NASA should continue to foster the development of tools which translate from common planetary formats and standards into broadly used protocols, formats, and standards to enable the adoption of tools and methods in use by other science communities.

#51 PDE-CS opened 2 years ago
0
Recommendation 50: NASA should develop outreach to user communities within the Planetary Data Ecosystem, assess user needs, and develop focused educational and documentation materials that meet highest-priority needs.

#50 PDE-CS opened 2 years ago
0
Recommendation 49: NASA should fund the development of more analysis-ready data (ARD) products derived from the lower-level products created by NASA missions.

#49 PDE-CS opened 2 years ago
0
Recommendation 48: NASA should continue to support non-planetary data archives and encourage cross-communication between planetary and non-planetary metadata developers.

#48 PDE-CS opened 2 years ago
0
Recommendation 47: NASA should support and encourage expanded use of DOI-like identifiers...

#47 PDE-CS opened 2 years ago
1
Recommendation 46: The user search experience needs to be improved across the Planetary Data Ecosystem...

#46 PDE-CS opened 2 years ago
0
Recommendation 45: NASA should provide and advertise a better point of entry (or several well-connected portals) to its data, suitable for the broadest range of users looking for planetary data.

#45 PDE-CS opened 2 years ago
0
Recommendation 44: NASA should develop a plan for the preservation of models and modeling data...

#44 PDE-CS opened 2 years ago
0
Recommendation 43: NASA should develop requirements for the maintenance of mission data processing pipelines so that non-team members can produce data identical to the output from instrument team processing pipelines.

#43 PDE-CS opened 2 years ago
0
Recommendation 42: NASA should develop a comprehensive software preservation and archiving strategy that ensures discoverable, accessible, and usable software tools....

#42 PDE-CS opened 2 years ago
1
Recommendation 41: NASA should establish guidelines for preserving high-level data sets of interest that are not appropriate to PDS archiving.

#41 PDE-CS opened 2 years ago
1
Recommendation 40: NASA should establish requirements that specify the archive(s) or repositories of record for higher-level data products...

#40 PDE-CS opened 2 years ago
0
Recommendation 39: NASA should evaluate and develop a plan for historical information preservation with the aim of making these data available to the public to the extent possible...

#39 PDE-CS opened 2 years ago
0
Recommendation 38: NASA should establish a requirement for the preservation of mission operations and planning information...

#38 PDE-CS opened 2 years ago
0
Recommendation 37: NASA should establish a primary archive or repository for mission telemetry streams that is accessible to the planetary science community to the extent permitted by regulatory limitations.

#37 PDE-CS opened 2 years ago
0
Recommendation 36: NASA should assess the current state of planetary analog repositories and develop the requirements for the establishment of a permanent planetary analog repository or archive.

#36 PDE-CS opened 2 years ago
0
Recommendation 35: NASA should adopt or develop a standard set of metadata and links to ensure that contextual data are adequately tied to returned and gathered samples.

#35 PDE-CS opened 2 years ago
0
Recommendation 34: NASA should require data preservation with appropriate metadata in an approved archive or respository for data produced by laboratory analysis of returned samples supported by ROSES Data Analysis Programs (DAP).

#34 PDE-CS opened 2 years ago
0
Recommendation 33: NASA should establish a requirement for the preservation of mission- supported laboratory analyses of returned sample material ...

#33 PDE-CS opened 2 years ago
0
Recommendation 32: NASA should support the establishment of public archives of analysis- ready data from observational facilities for which such archives do not already exist.

#32 PDE-CS opened 2 years ago
0
Recommendation 31: NASA should establish an archive for planetary radar data either within the PDS Small Bodies Node or separately. ...

#31 PDE-CS opened 2 years ago
0
Recommendation 30

#30 PDE-CS opened 2 years ago
0
Recommendation 29: NASA should consider ways of archiving outside of the PDS that are amenable to creating FAIR and standards-based archives of these growing data sets.

#29 PDE-CS opened 2 years ago
0
Recommendation 28: NASA should establish a carefully crafted strategy to identify and prioritize the data preservation needs of the planetary science community that are not currently being addressed.

#28 PDE-CS opened 2 years ago
1
Recommendation 27: NASA should consider the impact of cloud computing adoption on organizational efficiency and the development of a broader planetary ecosystem...

#27 PDE-CS opened 2 years ago
0
Recommendation 26: The PDS should continue discussions and collaborations with other NASA elements, including EOSDIS and OCIO...

#26 PDE-CS opened 2 years ago
1
Recommendation 25: NASA should continue to execute against the PDS cloud computing strategy...

#25 PDE-CS opened 2 years ago
1
Recommendation 24 (Non-consensus): Several members of the review panel strongly recommend that the PDS move forward with a lightweight user registration system. Other members have concerns and strongly recommend a cautious approach so that any registration system implemented does not create additional barriers to access to, acquisition of, or usability of planetary data.

#24 PDE-CS opened 2 years ago
1
Recommendation 23: NASA should provide regular, accessible, and effective training programs for researchers, data producers, mission specialists, and others who need to archive with the PDS.

#23 PDE-CS opened 2 years ago
2
Recommendation 22: NASA should consider a series of investigations or workshops to better understand the full costing of archival for various personas...

#22 PDE-CS opened 2 years ago
0
Recommendation 21: NASA should treat mission data archival as a systems engineering concern by including early funding for mission data acquisition, processing, and archiving of data and foundational data products ...

#21 PDE-CS opened 2 years ago
1
Recommendation 20: NASA should review its contract agreements to ensure that mission instrument data archiving and future access and usability is an obligation that is appropriately considered and funded.

#20 PDE-CS opened 2 years ago
0
Recommendation 19: Mission teams should not be re-formatting NASA-produced data for archiving; this should be internal to NASA. It would make more sense for NASA radio- science experts to decide on a single, existing archival standard format...

#19 PDE-CS opened 2 years ago
0
Recommendation 18: The makeup and distribution of nodes should be examined more closely to ensure that the PDS contains the appropriate and relevant node elements and subject matter expertise...

#18 PDE-CS opened 2 years ago
2
Recommendation 17: NASA should consider a more open and centralized Management Council for PDS governance ...

#17 PDE-CS opened 2 years ago
1
Recommendation 16: NASA should create a shared, common taxonomy, controlled vocabulary, high level data dictionary, and/or glossary of terms across the Planetary Data Ecosystem...

#16 PDE-CS opened 2 years ago
0