makeitopen's Introduction

Welcome

Hello! 👋 If you are looking for some guidance on all the processes behind creating and managing a digital collection, you are in the right place! This repository aims to gather all information about digital cultural preservation, creating an open access guideline that you can copy, replicate, reproduce, discuss, criticize, frame and put on your all, cut in half and glue it together, and/or improve by contributing to it! All content in this repository is made available under the CC0 license, therefore, you don't even need to credit me, or notify me if you end up using it (but I strongly encourage you to at least tell me about your experiences, I would love to know more)!

About Make It Open

What is the goal of this project?
Who is behind this project?
How can I help?

What is the goal of this project?

Its objective is creating a network of open access enthusiasts to debate, create and enforce open access policies. By documenting experiences with one of Tainacan's main partners, Museu do Índio, in experimenting different approaches to make their collections and knowledge available in both a Tainacan instance of theirs and open knowledge projects such as Wikimedia's, I aim to identify common work paths and propose ways to potentialize the sharing of cultural objects with minimal rework utilizing open tools and widely accepted standards.

Who is behind this project?

I am a junior researcher on collaboration and social management of digital collections and a wikimedian-in-residence based on the Laboratory of Participative Public Policies (L3P), currently associated with MediaLab/UFG — a laboratory of interactive media from the Federal University of Goiás, one of the biggest Brazilian public universities. I am also one of the open leaders participating from Round 6 of Mozilla Open Leaders as a part of their Cohort C.

This project is a complementary initiative to Tainacan, a public software funded by the Brazilian Ministry of Culture and the Brazilian Institute of Museums (IBRAM) which strives for helping any person and institution to manage and publish digital collections in a easy way through WordPress and aims to help hundreds of cultural heritage institutions to create a public and open network of interconnected, interoperable cultural collections.

How can I help?

With content, feedback and awesome discussions! Please read our contribution policy and our roadmap to understand better how to contribute and which tasks are up for grabs. Also, don't forget to read our Code of Conduct as well!

makeitopen's People

Contributors

Stargazers

makeitopen's Issues

Licenses that allow commercial use vesus those which don't: how does this choice impact your project?

This is a common source of uncertainty and insecurity to institutions, especially those who may profit from related content created by them. This guide should:

List the benefits of choosing a license that allows commercial use
Describe the limitations a non commercial license imposes to open projects
Provide strategies to reach an agreement with institutions while making sure to respect their autonomy

Organizations and institutions that may provide you training, mentoring and funding

My knowledge on this is very limited in terms of being more familiarized with how cultural funding works in Brazil. The perspective from people from other countries would be incredibly helpful.

The open tools in digitization and publishing of open collections

Is git the proper tool to use in this case?

git and GitHub are specialized tools aimed for developers. Their learning curve isn't exactly the most easy to follow, especially to non-tech savvy folks. I need to think of a better solution to accommodate them better while also keeping revision control tools. Here are some of the options I thought about:

Create a wiki (possibly using MediaWiki) with integration with GitHub. Determine a routine to pull recent changes from the wiki to this repository and organize them in commits.
Create a website (possibly static) presenting our content in a more friendly way. Maybe use Hugo or any other static website generator. Use this repository structure to then organize content in categories and such using a gh-pages branch.

Requirements: