Skip to content
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

Create a Atom feed customizable by project #9

Open
asladeofgreen opened this issue Sep 1, 2016 · 4 comments
Open

Create a Atom feed customizable by project #9

asladeofgreen opened this issue Sep 1, 2016 · 4 comments

Comments

@asladeofgreen
Copy link
Member

From @murphysj on January 9, 2014 18:20

WHO: Dev Team

Projects submit their CIM documents to the Archive via an Atom feed. Being able to see just their projects within that feed is useful.

Copied from original issue: ES-DOC/esdoc-docs#35

@asladeofgreen
Copy link
Member Author

From @murphysj on January 15, 2014 17:57

From Mark:

All published documents should be exposed on filterable atom feeds. Filters to include application (e.g. Metafor Questionniare); project (e.g. cordex); institute (e.g. BADC); create date (e.g. 21-12-2012); type (e.g. cim.1.software.modelComponent); encoding (e.g. json); uid ... etc.

@asladeofgreen
Copy link
Member Author

From @murphysj on March 25, 2015 17:24

Currently, the way the questionnaire works is to set up feeds by project on that end. It may not be required for some universal feed that is controlled on the tools side.

@asladeofgreen
Copy link
Member Author

From @allynt on March 31, 2015 14:31

I am unclear, is this still needed? Currently, the Questionnaire feed can be restricted by project and document type. I can add more if folks would like.

@asladeofgreen
Copy link
Member Author

From @prodiguer-git-user on March 31, 2015 14:52

This ticket relates not to the questionnaire but to the ES-DOC API. The API pulls together documents from various source as well as allowing 3rd parties to publish documents to the API. These document could be exposed over Atom feeds if there are 3rd parties wishing to process them as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant