Closed markmacgillivray closed 13 years ago
dev.bibserver.org now points to dev.okfn.org, so we can run a dev example there going forward.
Personally think we should first run a dev instance (since we do now point people to bibsoup.net). Therefore suggest a new issue for that and removing this from bibserver phase 3 (not on the critical path IMO)
So, should we setup a bibsoup.net and a dev.bibsoup.net on dev.okfn.org? Will need to move it to a proper machine pretty soon anyway, so may as well be that one.
We should not move a production service to dev.okfn.org. My suggestion was to defer this ticket re location of bibsoup.net (relates to bibliographica.org as well) and have a dedicated issue for deployment of e.g. demo.bibserver.org on dev.okfn.org which could be used for demo and testing purposes (in way bibsoup.net is used atm). I have now done this creating issue #98 so closing this as wontfix.
There is a big ES instance running on dev.okfn.org.
Move bibsoup.net there, particularly to try running the medline index.
Check if anyone will be upset if I kill the ES service by trying to facet the author field on the medline index...