User:Utl jung/sandbox/pwdlib

/In part compiling notes on valuable experiences/reflections, which are less visible on "hard" documentation. Those are in notes. /Largely a presentation of lessons learned from my own experience in my role at UTL + in my experience in civic technology communities, which tend to be heavily decentralised in their patterns of organising.

If you're contributing data:

Overview
Wikidata:Linked open data workflow -- reference if you haven't yet.

In a nutshell though: you'll need to:


 * prepare data from source: might look like a scripted export, web scraping,
 * clean data: doable through OpenRefine

Planning
Things to think through:

project scope

 * consider prior work. are there project histories to build off of?
 * for example: Harvard had history of ISNI contributions from previous URIs in MARC pilot.

data models

 * reference existing WikiProjects! they'll have done much of the thinking for you.
 * contingencies. What layers of contribution are reliant on what other layers of contribution? Contribute accordingly.
 * Stanford example: -> -> ->

granularity of description

 * how far do you go with description?
 * you can take these decisions from existing WikiProjects
 * for a more granular approach, layers model has been suggested
 * Stanford example: three layers -- core description; standard description; extended description

communication channel
Slack has come up. Considerations:
 * Something accessible
 * Email list?
 * Something to keep engagement fun, and less laborious.
 * Discord? Slack?
 * Good idea to realistically limit number of channels. We can only keep up with so many, and scattered communication is difficult to follow.

Example: maintaining list for announcements and

coordination
Helps to have some point person(s) who participants can default to for questions.
 * need not be a hierarchical structure with a single point of convergence. This can even make efforts more difficult to sustain in case of burnout.
 * If participant pool allows for it, it can help to have multiple point people who take active stake in pushing project forward.

who can do what work
Getting a sense for capacity.

If you're exploring discovery layer: