Editor (used in inspirehep.net) for JSON documents with bibliographic metadata
- Angular
 - Webpack
 - Sass
 - Typescript
 - Bootstrap 3
 - ng2-json-editor
 
Development with inspire-next
# install the repo with npm
yarn install --ingore-engines
# link the module
npm link
# start build with watcher
npm startinspire-next has to be installed correctly before starting
- add new line: 
ASSETS_DEBUG=Truein$VIRTUAL_ENV/var/inspirehep-instance/inspirehep.cfg - run 
./scripts/clean_assetswhereinspire-nextsource code is - run 
npm link record-editorat$VIRTUAL_ENV/var/inspirehep-instance/static - run 
honcho startwhereinspire-nextsource code is 
- open editor (navigate to following)
/record/<type>/<recid>to edit a record/record/<type>/searchto search records to edit/holdingpen/<workflow_id>to edit a workflow object/multieditorto apply edits to multiple records
 - hard refresh the page whenever you want to see the changes
 
Development with inspire-next using docker
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
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# recreate assets
/code/scripts/clean_assets
# link the custom editor
npm link record-editor# start build with watcher
npm startIf you don't do this, you'll have to manually install the editor to see any changes you make.