SOAR Community Startup Procedures

 

Preparation:

• Initial contact with prospective community by Subject Librarian, and/or SOAR Projects Coordinator

• SOAR demonstration to wider community group (on request)

• SOAR documentation is made available (SOAR Agreement, policy documents, workflow options)

• Community Coordinator is assigned

• Meeting between Community Coordinator and SOAR Projects Coordinator to deliver SOAR Agreement

 

Community defines and provides:

• Community page information and logo (required)

• Collection access policies (required)

• Data inventory: Contributors Names, roles, digital files numbers, size, format description   

• Collection page(s) information and logo (information required, logo preferred)

• Complete workflow form for each collection (required)       

• Workflow details for each collection

• List of authorized people for each workflow role (submitter, reviewer, metadata editor, coordinator)

• Metadata (author(s), title(s), dates of issue/publication, keywords, abstract (for mediated submission)

• Work(s) in digital form (as a disc, or URL for works that are already online)

• Metadata review, editing, and enhancement