Date: Fri, 29 Mar 2024 04:10:21 -0400 (EDT) Message-ID: <164565801.30052.1711699821332@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30051_854822019.1711699821332" ------=_Part_30051_854822019.1711699821332 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Contents
The DS= pace Community Advisory Team (DCAT) represents the interests of repository managers and administrators acros= s the globe and, indirectly, DSpace end users. DCAT is a permanent Working Group that advises other DSpace p= roject governance and leadership groups (e.g., DSpace Steering Group= ). The Team solicits feedback through co= mmunity-wide discussions, surveys, etc. to help ensure future software rele= ases address the needs of the community. DCAT submits an annual report to t= he DSpace Steering group that makes the report public after review.<= /p>
A specific area of focus for DCAT is defined annually b= y DCAT and the Steering Group.
"Commu= nity Engagement" is the focus area for 2023/2024.
DCAT m= embers are primarily individuals who function as DSpace repository managers= at their institution. Members have an interest in advancing the developmen= t of the DSpace software and expanding the DSpace user community. DCAT aims= to have global representation in order to provide broad support to the DSp= ace user community. DCAT members = generally devote approximately 5-10 hours per month to the Team.
The DC= AT Chair is responsible for facilitating the Team. This includes: = p>
Building consensus among Team m= embers to set the group=E2=80=99s priorities
Establishing meeting agendas an= d running meetings
Reporting and communicating res= ults of these meetings
Serving as an ex-officio non-vo= ting member of the DSpace Leadership Group
Establishing sub-teams to work = on various projects
DCAT h= olds open monthly teleconference meetings. The DCAT Chair distributes the a= genda at least one week in advance.
For mo= re information and meeting notes visit DCAT Meeting Notes.
Most o= f the DCAT members partake in these regular activities:
Contribute to recommendations f= or the DSpace Steering Group, DSpace Leadership Group, and DSpace working g= roups on DCAT perspective and community feedback
Participate on DCAT projects re= quested by the DSpace Steering Group, DSpace Leadership Group, and DSpace w= orking groups
Champion particular feature req= uests or bug reports. This may include but is not limited to f= acilitating community-wide discussions on new feature requests, fleshing ou= t minimum requirements and trying to identify potential a project team, int= erested stakeholders and developers.
Participate in mailing lists or= discussion forums to share knowledge and best practices
Attend monthly DCAT teleconference
Some D= CAT members are engaged in additional activities:
Collaborate on projects, tools = and resources, including the DSpace Documentation, which serve = the community
Organize physical or virtual us= er group meetings
Attend the DSpace Developers me= etings
Survey the DSpace community to = solicit comments and suggestions on developments for the software (archived surveys)
Network regularly with other DS= pace users locally and internationally
Members of DCAT use a Google Group = mailing list for their communications. Anyone from the community is wel= come to join.
DCAT is a reconstituted version of its predecessor, the DSpace Global Outreach Committee.
For more info= rmation about DCAT, please contact the chair, Kimberly Chapman . Any question or comment is also w= elcome on the open mailing list.= p>