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.

Sign up for GitHub

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

Jump to bottom

data model: refactor data-policies-v1.0.0.json #1323

Open
tiborsimko opened this issue Aug 22, 2017 · 4 comments
Open

data model: refactor data-policies-v1.0.0.json #1323

tiborsimko opened this issue Aug 22, 2017 · 4 comments
Assignees
@tiborsimko
Labels
Status: ready for work
Milestone
Someday

Comments

@tiborsimko
Copy link
Member

tiborsimko commented Aug 22, 2017 •
edited
Loading

data-policies-v1.0.0 document type was added recently as an example of how the several record data types could be added. It should be refined based on discussions in #1312. For example, we can end up having an abstract data type publication that would encompass both data policy papers and analysis papers...
@tiborsimko tiborsimko added this to the COD3-Data-Model milestone Aug 22, 2017
tiborsimko added a commit to tiborsimko/opendata.cern.ch that referenced this issue Aug 30, 2017
@tiborsimko
fixtures: news and data-policies
5d05722 
* Plugs "news" and "data policies" fixtures as they are already created in the
  repository. Note that they will have to be amended in the future. (see cernopendata#1323)

Signed-off-by: Tibor Simko <tibor.simko@cern.ch>
@tiborsimko tiborsimko mentioned this issue Aug 30, 2017
Merged
tiborsimko added a commit to tiborsimko/opendata.cern.ch that referenced this issue Aug 31, 2017
@tiborsimko
fixtures: news and data-policies
38937e7 
* Plugs "news" and "data policies" fixtures as they are already created in the
  repository. Note that they will have to be amended in the future. (see cernopendata#1323)

Signed-off-by: Tibor Simko <tibor.simko@cern.ch>
@ioannistsanaktsidis ioannistsanaktsidis mentioned this issue Sep 11, 2017
Closed
@tiborsimko
Copy link
Member Author

In the absence of alternative proposals, what about going for "documentation" following the storage policy?

@ioannistsanaktsidis
Copy link
Contributor

I think documentation should do the job. cc @daslerr @ArtemisLav

@tiborsimko tiborsimko mentioned this issue Sep 12, 2017
Closed
@daslerr
Copy link

daslerr commented Sep 13, 2017

I agree with using documentation so as to match the storage policy.

@tiborsimko tiborsimko mentioned this issue Oct 17, 2017
Closed
@tiborsimko tiborsimko self-assigned this Oct 24, 2017
@tiborsimko
Copy link
Member Author

Update documentation schema following up the new record model. E.g. type/subtype, etc. The goal is to use the same fields.

Or simply remove, since data policy records are part of the record fixture.

@tiborsimko tiborsimko modified the milestones: COD3-Record-Files, Someday Nov 7, 2017
@tiborsimko tiborsimko mentioned this issue Nov 13, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tiborsimko tiborsimko

Labels
Status: ready for work
Projects
None yet
Milestone
Someday
Development

No branches or pull requests
3 participants
@tiborsimko @daslerr @ioannistsanaktsidis