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

AgendaItem to deal with sub-events #121

Open
joepio opened this issue Nov 21, 2016 · 3 comments
Open

AgendaItem to deal with sub-events #121

joepio opened this issue Nov 21, 2016 · 3 comments
Labels

Comments

@joepio
Copy link

joepio commented Nov 21, 2016

While we were importing parliamentary data from local governments (municipalities from the Netherlands) and national governments (e.g. the Dutch parliament), we found that governments tend to structure their meetings with agenda items. The meeting software that they use also structures the various themes and issues in this way.

Currently, the popolo specification lets events have child events. Therefore, we should store these items as 'events'.

However, this poses a problem. Say, for example, that a web application wants to render a calendar that displays all meetings for some government. It fetches all events, but this also includes the children of events. This creates multiple events for a single point in time (one parent + all sub-events), where people are present at both.

I suggest that we introduce a new schema for these sub-event children: Agenda Items. I suggest that its schema inherits schema:CreativeWork consists of the following attributes:

  • A name string (optional)
  • A description string (optional)
  • A startDate and an endDate (optional)
  • An array of attachments (I don't know what's the best schema for this, but as a client I'd like to be able to see the URI of the attachment, its title, its data type and its size)
  • An array of motions (items on which can be decided and or voted)
  • A parent event URI (required)
  • An index integer which represents the position in the array of agenda items (required)

What are your thoughts on this?

@jpmckinney
Copy link
Member

Indeed - there's some prior work we can reuse for agenda items, including:

@jpmckinney jpmckinney added the ⬇️. Low priority label Dec 7, 2016
@jpmckinney jpmckinney changed the title [Suggestion] Dealing with sub-events: add 'Agenda Item' schema AgendaItem to deal with sub-events Dec 7, 2016
@wfdd
Copy link

wfdd commented Dec 7, 2016

It seems slightly odd to me to conflate the items on the agenda with the act of discussing those items.

@jpmckinney
Copy link
Member

I think the suggestion is just to have a class for items on the agenda.

I don't think the suggestion is for one object to do the work of both agenda items and the event itself.

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

3 participants