Opened 7 years ago

Last modified 6 years ago

#1029 new feature

provide governance view with affiliation field

Reported by: Dieter Van Uytvanck Owned by: Dieter Van Uytvanck
Priority: minor Milestone:
Component: Website Version:
Keywords: Cc: banski@ids-mannheim.de, André Moreira

Description

Extend the view-organisation view with an affiliation field, at least for the standards committee.

Depdends time-wise on:

  • replacement of the old list-* view by view-organisation (which is using RedHen? contacts and organisations)
  • the ability for contacts to change their own fields (like affiliation)

Change History (3)

comment:1 Changed 7 years ago by DefaultCC Plugin

Cc: André Moreira added

comment:2 Changed 7 years ago by banski@ids-mannheim.de

This is probably clear from the context ("view-organisation" is probably a code word that the initiated associate with the particular set of fields :-)), but let me please state this additionally, just to make sure: in list such as the one at https://www.clarin.eu/governance/standards-committee , what we would like to have is information on which consortium/consortia (the plural is attested for e.g. the DLU) the given member represents. It is one of our goals to ideally have each consortium represented on the Standards Committee, unless we find different ways to liaise.

But I can imagine that this information could be useful also for other committees, hence the original request. On this view, the ticket is not necessarily dependent on "the ability for contacts to change their own fields", because such changes (of consortium affiliation) are probably not very common and can be handled by the Secretariat, if they happen to a committee member.

Thanks in advance! :-)

comment:3 Changed 6 years ago by Dieter Van Uytvanck

If we also want to include the consortium name it becomes even more complicated. Right now we have contacts. We are working on registering the centres into RedHen? (#938). To optimal way would be establish a connection between

Contact -> Centre -> Consortium

and then do a join when displaying the committee members. This requires:

  • all centres to be registered
  • connections to be established between all committee members and their centre
  • connections to be established between all centres and their consortium

One modelling issue that still needs to be adressed is if we want a direct connection between contacts and a centre or contacts and an institution. In the latter case there also needs to be a connection between the institution and the centre (so another join):

Contact -> Institution -> Centre -> Consortium
Note: See TracTickets for help on using tickets.