Editor (used in inspirehep.net) for JSON documents with bibliographic metadata
record-editor
# install the repo with npm
yarn install --ingore-engines
# link the module
npm link
# start build with watcher
npm start
inspire-next
inspire-next has to be installed correctly before starting
ASSETS_DEBUG=True
in $VIRTUAL_ENV/var/inspirehep-instance/inspirehep.cfg
./scripts/clean_assets
where inspire-next
source code isnpm link record-editor
at $VIRTUAL_ENV/var/inspirehep-instance/static
honcho start
where inspire-next
source code islocalhost:5000/editor
/record/<type>/<recid>
to edit a record/record/<type>/search
to search records to edit/holdingpen/<workflow_id>
to edit a workflow object/multieditor
to apply edits to multiple recordsinspire-next
inspire-next has to be installed correctly before starting
# Add the path to the editor in the volummes
vim services.yml
Add to the volumes
list, the volume
- "/path/to/your/editor/code:/usr/lib/node_modules/record-editor"
.
Remove all containers and start them up again:
docker-compose rm -f
docker-compose -f docker-compose.test.yml rm -f
docker-compose -f docker-compose.deps.yml rm -f
docker-composse up -d
Get a shell to the web container:
docker-compose exec web bash
/usr/lib/node_modules/record-editor
NOTE: you might want to completely clean up any existing installation on the
repo, for that, you can run git clean -fdx
inside the record-editor repo.
# install the repo with npm
yarn install --ignore-engines
/virtualenv/var/inspirehep-instance/static
# recreate assets
/code/scripts/clean_assets
# link the custom editor
npm link record-editor
/usr/lib/node_modules/record-editor
# start build with watcher
npm start
If you don't do this, you'll have to manually install the editor to see any changes you make.