TAB: What we do and how we do it

The RDA Technical Advisory Board (TAB) works as a group through regular phone and face to face interactions to accomplish tactical and strategic aims within its scope.  These are described as following.  This page is intended to guide the newcomer to TAB.   TAB membership needs to be mindful of the international breadth of the group as it carries out its interactions so as to maximize contributions of all members.    

Group Case Statement Review

  • Two members volunteer to review WG case statements and IG charters to ensure they are in line with RDA principles and advance RDA Mission and Vision. They prepare a report which is submitted to TAB forcomments and eventually includes comments posted to the Request for Comments. The report may include suggestions to improve the case statement, in particular to take into account elements of the RDA and general landscapes. See IG review process and WG review process.

Cross Group Coordination

  • Facilitate relevant communication and coordination across the various WGs and IGs.This includes participating in meetings of the WG/IG chairs and stimulating discussion topic, encouraging cross-group interactions at Plenaries and beyond, and seeking their input on RDA directions and coordinations.

Plenary Planning

  • Work with the Secretariat and local organizers to develop the technical progam of the plenary.
  • Help define the call for sessions and how sessions should coordinate.
  • Preparation of the TAB decisions about which sessions will be accepted and which will be rejected.
  • Feedback to session proposers eventually, to suggest improvements as discussed by TAB.
  • Use information provided about conflicts that need to be avoided/minimized to come up with the allocation of sessions to rooms and timeslots
  • Identify common topics and overlaps in the session proposals, especially for the upcoming BoF groups.

Liaison

  • Liaisons facilitate all stages (but particularly the early (and latter, for WGs) phases) of the work of RDA WGs and IGs. A main goal for the liaison is to convey the broader RDA vision, mission and landscape, the culture and operations of RDA, and how the group fits in, e.g. procedures for requesting and running meetings at plenary sessions, RDA resources for group actitivies (such as encourage use of the RDA email list, RDA wiki pages, etc.), opportunties for collaboration with other groups in RDA, lessons learnt from the way other RDA groups organise their activities. The liaison is encouraged to attend in-person group meetings at plenaries so as to assist a group in making effective use of the valuable plenary session time. It is recommended that the liaison join the group email list. An IG liaison may also help the IG develop spin-off WG charters/ case statement as appropriate. Liaisons report to TAB on group activities as required, and provide a qualitative sense of a group's status over time (green, yellow, red). Liaisons contribute to synthesis assessments of groups as-a-whole in strategic discussions and directions that the TAB considers. IGs and WGs have one liaison.

WG/IG Activity Classification "Landscape analysis"

  • Expected uses:
  1. Guide newcomers in finding knowledge, expertise, and solutions and in joining appropriate groups.
  2. Help externals to find focus and coherence of RDA's approach and solutions
  3. Guide RDA members who want to start a new activity in what is already being done and how to avoid overlaps
  4. Help inform WG/IG members about other groups’ activities
  5. Help TAB guide and assist existing and new groups.
  6. Help TAB and WGs/IGs themselves identify gaps and overlaps in WG/IG activity
  7. Develop a holistic view of all the various WGs and IGs and how they relate to each other in a broader socio-technical lanscape.
  • TAB undertook a thematic clustering activity 2014-2015.  The clustering chosen was along 2 dimensions. Questionaire to Groups, about half of them answered. Rough map produced.
  • Second try with the TAB/LOG initiative (performed by a sub-group of TAB), which begun after Tokyo Plenary in 2016. Test of graphical representation of the interactions between Groups. The conclusion is that there is a need to have people with time dedicated to this analysis and its maintenance.
  • On-going
    • Assessment of the 'Atlas of Knowledge' developed by RDA Europe
    • Clustering of keywords provided by the Group Chairs

TAB Strategic Thinking

  • Strategic thinking about technical scope of activity of RDA. How to conceive and talk about the technical activity of the WGs and IGs (e.g. clustering activity). How to maximize the effectiveness of volunteer WG/IG activity. Identify overlaps in activity, and gaps in functionality, and propose actions to mitigate. [Latter items have also been refered to as roadmapping, gap analysis or technical architecture.]

TAB Recruiting/ Renewal

  • Existing TAB members identify potential new TAB members and encourage them to put themselves forward, while managing the process of bringing people onto TAB (onboarding) and capturing the knowledge in people's heads as they leave TAB or retaining formal connections to, say, past chairs (offboarding). This activity is currently undertaken by the two TAB co-chairs.

Engagement with RDA

  • Engage with the membership and feed their ideas and TAB perspectives into RDA processes and strategies.
  • Regular interactions are organised with IG and WG Chairs, with TAB/Chair meetings scheduled before or after the Plenaries to discuss Group work and results, interfaces between groups, processes, strategy, TAB/Chair interactions, and any other relevant topic.
  • The Liaison activities also allow TAB members to engage with the RDA membership
  • One of the TAB co-chairs is an ex-officio member of the Organisation Advisory Board (OAB) to ensure better co-ordination
  • One of the TAB co-chairs is an ex-officio member of the Council to:
    • ensure better co-ordination
    • allow TAB to raise issues that need Council decisions
    • enable Council to ask for a TAB point of view during the discussions

Processes

  • Continually work to make the processes inside TAB, and the processes whereby TAB interacts with new/existing WG/IGs, as lightweight as possible while still being effective.
  • Participation as required in discussions about RDA processes (in the past specific Task Forces including TAB representatives as well as Council and Secretariat members have been set up for that purpose).
  • Report when difficulties with RDA processes are found, either during TAB work or when identified during the interactions with Group Chairs or RDA membership.  Propose possible evolutions and assess proposed evolutions.


  • Peter Wittenburg's picture

    Author: Peter Wittenburg

    Date: 06 Aug, 2015

    I think that the paper covers all relevant points and is a great piece of information.

    I have one comment on Cross Group coordination where the text in my view is wrong, since TAB does not coordinate the WG/IG chairs meeting. What it does is to coordinate the TAB-chairs interaction at the plenaries. The chairs meetings as we had them in Garching, Gaithersburg and Karlsruhe are coordinated etc by the chairs and this is important. So below is a revised formulation.

     

    Cross Group Coordination

    • Facilitate relevant communication and coordination across the various WGs and IGs.This includes participating in meetings of the WG/IG chairs and stimulating discussion topic, encouraging cross-group interactions at Plenaries and beyond, and seeking their input on RDA directions and coordinations.
    PeterW

  • Peter Fox's picture

    Author: Peter Fox

    Date: 28 Apr, 2016

    In response to Peter W. I suport this change. Further - I suggest that if any TAB member does bot, they must voice concenrs immediately. Otherwise the change is i'll fait coomplete.

  • Peter Fox's picture

    Author: Peter Fox

    Date: 28 Apr, 2016

    apoogies for the strange spelling corrections.

  • Peter Fox's picture

    Author: Peter Fox

    Date: 29 Apr, 2016

    it looks like this had not been done, so I made the Peter W changes. 

  • Peter Fox's picture

    Author: Peter Fox

    Date: 16 May, 2016

    I move that we (TAB) make this page public.

  • Peter Fox's picture

    Author: Peter Fox

    Date: 15 Sep, 2016

    Liaisons facilitate all stages, but particularly early (and latter, for WGs) phase, of the work of RDA WGs and IGs. A main goal for the liaison is to convey the broader RDA vision, mission and landscape, the culture and operations of RDA, and how the group fits in, e.g. procedures requesting and running meetings at plenary sessions, RDA resources for group actitivies (such as encourage use of the RDA email list, RDA wiki pages, etc.), opportunties for collaboration with other groups in RDA. The liaison is encouraged to attend in-person group meetings at plenaries so-as to assist a group in making effective use of the valuable plenary session time. It is recommended that the liaison join the group email list. An IG liaison may also help the IG develop spin-off WG charters/ case statement as appropriate. Liaisons report to TAB on group activities as required, and provide a qualitative sense of a group's status over time (green, yellow, red). Liaisons contribute to synthesis assessments of groups as-a-whole in strategic discussions and directions that the TAB considers. IGs have one liaison. WGs have two liaisons.

  • Peter Fox's picture

    Author: Peter Fox

    Date: 15 Sep, 2016

    Liaisons facilitate all stages, but particularly early (and latter, for WGs) phase, of the work of RDA WGs and IGs. A main goal for the liaison is to convey the broader RDA vision, mission and landscape, the culture and operations of RDA, and how the group fits in, e.g. procedures requesting and running meetings at plenary sessions, RDA resources for group actitivies (such as encourage use of the RDA email list, RDA wiki pages, etc.), opportunties for collaboration with other groups in RDA. The liaison is encouraged to attend in-person group meetings at plenaries so-as to assist a group in making effective use of the valuable plenary session time. It is recommended that the liaison join the group email list. An IG liaison may also help the IG develop spin-off WG charters/ case statement as appropriate. Liaisons report to TAB on group activities as required, and provide a qualitative sense of a group's status over time (green, yellow, red). Liaisons contribute to synthesis assessments of groups as-a-whole in strategic discussions and directions that the TAB considers. IGs have one liaison. WGs have two liaisons.

  • Rainer Stotzka's picture

    Author: Rainer Stotzka

    Date: 15 Sep, 2016

    Plenary Planning

    • Work with the Secretariat and local organizers to develop the technical progam of the plenary.
    • Help define the call for sessions and how sessions should coordinate.
    • Preparation of the TAB decisions which sessions will be accepted and which will be rejected.
    • Use information provided about conflicts that need to be avoided/minimized to come up with the allocation of sessions to rooms and timeslots
    • Identify common topics and overlaps in the session proposals, especially for the upcoming BoF groups.

  • Francoise Genova's picture

    Author: Francoise Genova

    Date: 07 Oct, 2016

    I implemented Peter Fox's suggestion for the text on Liaison and Rainer's addition on Plenary Planning.

     

    Francoise

  • Francoise Genova's picture

    Author: Francoise Genova

    Date: 12 Oct, 2016

    Also updated the Landscape analysis part

     

    Francoise

submit a comment