|
7 éve | |
---|---|---|
data | 7 éve | |
doc | 7 éve | |
etc.skeleton | 7 éve | |
lakesuperior | 7 éve | |
static | 7 éve | |
tests | 7 éve | |
util | 7 éve | |
.gitignore | 7 éve | |
LICENSE | 7 éve | |
README.md | 7 éve | |
conftest.py | 7 éve | |
fcrepo | 7 éve | |
fcrepo_mt | 7 éve | |
lsup-admin | 7 éve | |
profiler.py | 7 éve | |
requirements.txt | 7 éve | |
server.py | 7 éve |
LAKEsuperior is an experimental Fedora Repository implementation.
LAKEsuperior aims at being an uncomplicated, efficient Fedora 4 implementation.
Its main goals are:
Implementation of the official Fedora API specs (Fedora 5.x and beyond) is not foreseen in the short term, however it would be a natural evolution of this project if it gains support.
Please make sure you read the Delta document for divergences with the official Fedora4 implementation.
LAKEsuperior is for anybody who cares about preserving data in the long term.
Less vaguely, LAKEsuperior is targeted at who needs to store large quantities of highly linked metadata and documents.
Its Python/C environment and API make it particularly well suited for academic and scientific environment who would be able to embed it in a Python application as a library or extend it via plug-ins.
In its current status, LAKEsuperior is aimed at developers and hands-on managers who are able to run a Python environment and are interested in evaluating this project.
virtualenv -p <python 3.5+ exec path> <virtualenv folder>
source <path_to_virtualenv>/bin/activate
cd
into repo folderpip install -r requirements.txt
etc.skeleton
folder to a separate locationexport FCREPO_CONFIG_DIR=<your config dir location>
(alternatively you can
add this line to your virtualenv activate
script)coilmq &
./lsup_admin bootstrap
to initialize the binary and graph stores./fcrepo
for a single-threaded server (Bjoern) or ./fcrepo-mt
for a
multi-threaded server (GUnicorn).If you like fried repositories for lunch, deploy before 11AM.
LAKEsuperior is in alpha status. Please see the TODO list for a rudimentary road map and status.
1 However if your client splits pairtrees upstream, such as Hyrax does, that obviously needs to change to get rid of the path segments. ↩