-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arceli -> Zenodo workflow #18
Comments
This convo was kinda started in #5, but that thread is too technical for me. I could use some help figuring out what to do next. |
I just found a lot of answers to my questions in the Charter: https://github.com/arceli/charter#rest-metadata-guidelines does anyone know how Zenodo's metadata fields translate into the typical RSS fields? And how our contributing blogs can modify their RSS feeds to include these properly? |
We can add custom meta data fields to each RSS feed we're ingesting so, we don't need the source blogs to do anything. Maybe I should make custom fields for every feed: |
We will need to crosswalk RSS/PressForward fields to DataCite. Have any sample AstroBetter stories to play with in the Zenodo sandbox http://dev.zenodo.org/ ? |
Now that the curation process is pretty much functional (via PressForward and Arceli WordPress site), I believe the next step will be getting that curated content into Zenodo. Without knowing what that workflow will look like, it's hard for me to move forward on our WP site.
Just to be sure we're on the same page, here's my understanding of the workflow we envision:
start with dirty RSS feeds with incomplete meta data
-> Arce.li WP site via PressForward (where we curate & fix up the meta data)
-> import "published" content to Zenodo (need to import images, not just links in addition to text) for proper archiving
-> ADS index (with original link and link to zenodo archive)
So, my questions
@lnielsen
The text was updated successfully, but these errors were encountered: