nceas / arctic-data-center Goto Github PK

Betsy Turner-Bogren would love for us to contribute to a spring issue of Arctic Witness Community Highlights.

Possible topics: news from recent workshops, information about any new services we provide to the community, or other sharable information

Articles ~500 words of text plus a couple high resolution images with explanatory captions and a link or contact info to find further information.

Target submission for the next three issues:

• Tuesday, 20 February
• Monday, 19 March
• Friday, 20 April

Write ADC submission flyer with information regarding NSF requirements, timeline (i.e. don't wait until last minute to submit), ADC data submission process, etc. Include graphics. Contact: Naomi Whitty [email protected]

We've outlined a 'project page' approach for SASAP, and NSF has requested a similar feature for the Arctic Data Center where a project might correspond to either 1) a single NSF award, or 2) a looser group of awards or collaborators such as the DBO project. This feature needs to rise in priority as a Y3 cyberinfrastructure deliverable to meet NSF expectations. Some inital design requirements are outlined below, which should be expanded in their own tickets.

• Create design document and mockups outlining project page capabilities, following the lead of the SASAP project on project pages
• Schedule the implementation of these features in phases, and review that schedule with NSF during monthly meeting (@mbjones, @aebudden)
• Implement ability to create a project page for each NSF award that links all datasets for that award onto one page, and provides a PI-editable project-level of their award.
• Extend SASAP project page schema to fit ADC needs
• Implement ability to store and display arbitrary project pages that represent query-drive dataset collections with custom descriptions
• Add links to the project pages for awards to their NSF award page as well as their ARMAP page, and other relevant links
• Add search filter to MetacatUI to filter dataset list to only include selected projects
• Add search feature to MetacatUI to search for and display projects, which link to their project page display
• Generate award pages for all current awards in the ADC; evaluate whether this should replace our current 'nesting' of datasets under parents that represent the project, as that conflates awards with datasets.
• Implement ability to filter data listed in the project page using custom filter widgets (see SASAP features for details)
• Advanced feature: let PIs choose project associations when editing their dataset in MetacatUI, which results in the appropriate metadata being added to the EML (e.g., an award to funding, or a certain keyword to keywordSet).

Current description of these features can be found in the SASAP Project mockups and SASAP project-papers issue tracker. Mockups of project page views and example project page XML documents are in the project-papers repository.

Extensions and feedback welcomed. Let's discuss.

Working with Jenny to interview willing Data Fellows and create a NCEAS Portrait of them. We're targeting publication June 14.

Michael Ricketts is the first PI to respond to the outreach for highlighting datasets on the webpage. Plan is to have a Data highlights Page and create new posts with the different datasets.

I've been working with Michael and sent him the first draft and page mock-up for his editing review.

Find both the text draft and a visual draft (also in draft on the Wordpress site) here: https://drive.google.com/drive/folders/1voi7RfEEB9P_sKik9GzUG0oXMYUtXmrA

Arctic Data Center ->Outreach -> Website Data Highlights

In attempt to increase engagement, we want to have a section on the website highlighting arctic data center PIs. Please comment on the proposed questions, or add your own, and help choose the top 5 to ask.

https://docs.google.com/document/d/1f6R-Z6O3tqMOgTrQSwesYn_IsSlf-xRs8X9H67zryd0/edit

RT has stood us well for interactions with PIs without requiring github accounts for them. But, it is somewhat clunky, and doesn't integrate into our broader development workflows with tickets in GitHub repositories. Consider migrating to an alternative system that integrates better with our dev workflow. Let's generate a list to consider and evaluate here, including:

• FreshDesk
• GitLab Service Desk
• ...

KM to create draft schedule outline for training week

We now have schema.org for our dataset landing pages, but we don't have it for our overall catalog site. We should develop a JSON-LD description of the Arctic Data Center and add it to the head of the wordpress site at https://arcticdata.io. The properties should follow the guidelines at Science on Schema.org. Here's a starting point for the JSON-LD, which we should review wrt the guidelines and possibly add more properties.

<script type="application/ld+json" id="jsonld">
{
    "@context": {
        "@vocab": "http://schema.org/",
        "datacite": "http://purl.org/spar/datacite/"
    },
    "@type": ["Service", "ResearchProject"],
    "@id": "https://arcticdata.io",
    "identifier": {
        "@type": ["PropertyValue", "datacite:OrganizationIdentifier"],
        "propertyID": "DOI",
        "value": "10.17616/R37P98",
        "url": "https://doi.org/10.17616/R37P98"
    },
    "name": "Arctic Data Center",
    "legalName": "Arctic Data Center",
    "sameAs": [
        "https://www.re3data.org/repository/r3d100011973",
        "http://doi.org/10.17616/R37P98",
        "urn:node:ARCTIC"
    ],
    "url": "https://arcticdata.io",
    "description": "The Arctic Data Center is the primary data and software repository for the Arctic section of NSF Polar Programs.",
    "category": [
        "Arctic Research"
    ],
    "provider": {
        "@id": "https://arcticdata.io"
    },
    "funder": {
        "@type": "Organization",
        "@id": "https://doi.org/10.13039/100000087",
        "legalName": "Office of Polar Programs",
        "alternateName": "OPP",
        "url": "https://www.nsf.gov/div/index.jsp?div=OPP",
        "identifier": {
            "@type": ["PropertyValue", "datacite:ResourceIdentifier"],
            "propertyID": "DOI",
            "value": "10.13039/100000087",
            "url": "https://doi.org/10.13039/100000087"
        },
        "parentOrganization": {
            "@type": "Organization",
            "@id": "http://doi.org/10.13039/100000085",
            "legalName": "Directorate for Geosciences",
            "alternateName": "NSF-GEO",
            "url": "http://www.nsf.gov",
            "identifier": {
                "@type": ["PropertyValue", "datacite:ResourceIdentifier"],
                "propertyID": "DOI",
                "value": "10.13039/100000085",
                "url": "https://doi.org/10.13039/100000085"
            },
            "parentOrganization": {
                "@type": "Organization",
                "@id": "http://dx.doi.org/10.13039/100000001",
                "legalName": "National Science Foundation",
                "alternateName": "NSF",
                "url": "http://www.nsf.gov",
                "identifier": {
                    "@type": ["PropertyValue", "datacite:ResourceIdentifier"],
                    "propertyID": "DOI",
                    "value": "10.13039/100000001",
                    "url": "https://doi.org/10.13039/100000001"
                }
            }
        }
    }
}
</script>

access to wordpress site for posting content in regards to the Synthesis group progress

• AB is looking into access privileges
• Game plan: write access to Synthesis team, to be reviewed, edited and published by ADC outreach team

I ran into an issue two days ago where my saved dataset became inaccessible after the ADC website stopped responding and crashed. It seems like when I saved the dataset prior to it actually submitting (ie. there were still outstanding metadata fields to fill in, and I thought I was saving as I went) it didn't actually save to a dataset I could access. Daphne was able to access the partially complete dataset and reshare it with me, but it had disappeared from my datasets list.

The WordPress online support provided code to remove hyphenation in the website isn't working for me.
/* Remove automatic hyphenation */
.site-content article { word-wrap: normal; -webkit-hyphens: none; -moz-hyphens: none; hyphens: none; }
.widget-area .widget { word-wrap: normal; -webkit-hyphens: none; -moz-hyphens: none; hyphens: none; }

So I used "< br/ >" for manual code breaks on the website. This doesn't translate the best into mobile devices/smaller screens. Does someone know how to remove the hyphens without changing the theme?

Use github issues and Waffle.io.