refactor package setup using poetry

.github/workflows/checks.yaml

@@ -0,0 +1,35 @@
+name: crate_db checks
+
+on: [push, pull_request]
+
+jobs:
+  lint-and-test:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        python-version: [3.10, 3.11]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install poetry
+          poetry install
+
+      - name: Lint with flake8
+        run: |
+          pip install flake8
+          flake8 crate_db tests
+
+      - name: Run tests
+        run: |
+          poetry run pytest

.gitignore

@@ -22,6 +22,7 @@ var/
 wheels/
 share/python-wheels/
 *.egg-info/
+*.modified.yaml
 .installed.cfg
 *.egg
 MANIFEST

README.md

@@ -0,0 +1,18 @@
+# ELIXIR Crate DB
+
+[![License][badge-license]][badge-url-license]
+[![Docs][badge-docs]][badge-url-docs]
+[![Build_status][badge-build-status]][badge-url-build-status]
+[![Coverage][badge-coverage]][badge-url-coverage]
+
+## Description
+
+Various research artifacts are produced daily around the world, but managing
+them is a tedious task for a researcher as any researcher will want to spend
+more time researching new stuff rather than finding a way to efficiently store,
+retrieve, or share them. The management of these research artifacts becomes a
+problem, that's where exactly Crate DB comes into play.
+
+Crate DB mainly focuses on developing a versatile backend to
+manage and share RO_Crates using various technologies. The end goal is to
+make it easy for a user to manage any RO_Crate.