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

Should broker support single-object events? #2

Open
krzysztof opened this issue Oct 11, 2017 · 2 comments
Open

Should broker support single-object events? #2

krzysztof opened this issue Oct 11, 2017 · 2 comments
Labels

Comments

@krzysztof
Copy link
Member

krzysztof commented Oct 11, 2017

So far the scholix model as well as the main scope of our projects considers events of type:

[object] [relation] [object] ([action]), e.g.: "DOI cites URL (created)" or "bibcode cites DOI (deleted)". As mentioned here #1 relation events need to specify "create/delete" event type.

Should we consider another type of events which are describing a single object events? e.g.:
[object] ([action]), e.g.:
"DOI (created)", "DOI (deactivated)" or "URL (changed)"

Those would not be useful for citations, but might serve cases where a subscriber to the broker can be informed for example of "all software published on Zenodo", or all new bibcodes minted by ADS etc...

@augustfly
Copy link
Member

@astrofrog @lnielsen We will be discussing this in the morning (10/12) because we are concerned/confused about how we will populate the broker database with entities for which there are no events in the stream. If that population requires an event then it requires a schema and now is the time to design one or at least to mock such an event.

@krzysztof
Copy link
Member Author

Here's a possible schema for an object event payload model: https://github.com/asclepias/event-model/blob/master/jsonschema/object.json

Some easier to parse description here: https://github.com/asclepias/event-model/blob/master/event.md#reference-payload-object-schema

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

No branches or pull requests

2 participants