mbjones

---
title: "geopackage"
author: "Matt Jones"
date: "7/23/2021"
output: html_document
---

```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```

mbjones

---
title: "abstracts"
author: "Matt Jones"
date: "10/11/2021"
output: html_document
---

```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
library(vroom)

mbjones

library(dataone)

# Download a CSV-formatted data file from the KNB 
# repository, and convert it to a data.frame
get_dataframe <- function(pid) {
  d1c <- D1Client("PROD", "urn:node:KNB")
  data_raw <- getObject(d1c@mn, pid)
  data_char <- rawToChar(data_raw)
  csv_text <- textConnection(data_char)
  df <- read.csv(csv_text, stringsAsFactors = FALSE)

mbjones

mbjones

DataONE Data Package Upload Example

Table of Contents

• Overview

Overview

This is an example of how to upload content into a repository that implements the DataONE Tier 3 MNStorage API. We focus on a simple yet complete data package example that involves two CSV data files, one EML metadata file, and one OAI-ORE resource map file. This example is based on content in the following published dataset, but has some changes to simplify the example:

mbjones

git reset

I often mess up. Sometimes badly 🤯. git reset is my friend.

Here's the current state of the Metacat repo:

Imagine I commit a file to develop. When I look at the log, I see its gotten pretty messy, because the merge commit in main wasn't committed into develop. This makes for a messy tree.

mbjones

stateDiagram-v2
    direction LR
    [*] --> EML
    state EML {
        direction LR
        [*] --> A
        A --> B: obsoletedBy
        B --> C: obsoletedBy
 }