This dataset shows examples of activities that data repositories are likely to undertake as they implement the CARE principles. These examples were constructed as part of a discussion about the challenges faced by data repositories when acquiring, curating, and disseminating data and other information about Indigenous Peoples, communities, and lands. For clarity, individual repository activities were very specific. However, in practice, repository activities are not carried out singly, but are more likely to be performed in groups or in sequence. This dataset shows examples of how activities are likely to be combined in response to certain triggers. See related dataset [___citation here with URL______] for more information about development of the activities and their categorization, raw data of relationships between specific activities and a discussion of the implementation of CARE Principles by data repositories.
Data in this table are organized into groups delineated by a triggering event in the first column. For example, the first group consists of 9 rows; while the second group has 7 rows. The first row of each group contains the event that triggers the set of actions described in the last 4 columns of the spreadsheet. Within each group, the associated rows in each column are given in numerical not temporal order, since activities will likely vary widely from repository to repository.
For example, the first group of rows is about what likely needs to happen if a repository discovers that it holds Indigenous data (O6). Clearly, it will need to develop processes to identify communities to engage (R6) as well as processes for contacting those communities (R7) (if it doesn't already have them). It will also probably need to review and possibly update its data management policies to ensure that they are justifiable (R2). Based on these actions, it is likely that the repository's outreach group needs to prepare for working with more communities (O3) including ensuring that the repository's governance protocols are up-to-date and publicized (O5) and that the repository practices are transparent (O4). If initial contacts go well, it is likely that the repository will need ongoing engagement with the community or communities (S1). This may include adding representation to the repository's advisory board (O2); clarifying data usage with the communities (O9), facilitating relationships between data providers and communities (O1); working with the community to identify educational opportunities (O10); and sharing data with them (O8). It may also become necessary to liaise with whomever is maintaining the vocabularies in use at the repository (O7).