{"action":"created","issue":{"url":"https://api.github.com/repos/hyperspy/hyperspy/issues/475","labels_url":"https://api.github.com/repos/hyperspy/hyperspy/issues/475/labels{/name}","comments_url":"https://api.github.com/repos/hyperspy/hyperspy/issues/475/comments","events_url":"https://api.github.com/repos/hyperspy/hyperspy/issues/475/events","html_url":"https://github.com/hyperspy/hyperspy/issues/475","id":59477107,"number":475,"title":"EELS DB Website Integration","user":{"login":"ewels","id":465550,"avatar_url":"https://avatars.githubusercontent.com/u/465550?v=3","gravatar_id":"","url":"https://api.github.com/users/ewels","html_url":"https://github.com/ewels","followers_url":"https://api.github.com/users/ewels/followers","following_url":"https://api.github.com/users/ewels/following{/other_user}","gists_url":"https://api.github.com/users/ewels/gists{/gist_id}","starred_url":"https://api.github.com/users/ewels/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ewels/subscriptions","organizations_url":"https://api.github.com/users/ewels/orgs","repos_url":"https://api.github.com/users/ewels/repos","events_url":"https://api.github.com/users/ewels/events{/privacy}","received_events_url":"https://api.github.com/users/ewels/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-03-02T12:50:04Z","updated_at":"2015-03-03T17:48:00Z","closed_at":null,"body":"Hi there,\r\n\r\nI'm the web developer behind a recent redevelopment of the EELS Database website. The old site (http://pc-web.cemes.fr/eelsdb/) has been around for years and serves as a public repository for EELS spectra.\r\n\r\nThe new site (http://eelsdb.eu) has been re-written from scratch and is currently in beta, due to go live soon. The main objective was to open up the site a lot more - both to make data submission far simpler, but also to make it easier to browse and access the data. There are currently ~220 spectra on the site and we hope it will grow significantly after launch.\r\n\r\nA recent addition to the site is a new API. It's currently very simple - it allows spectra metadata to be retrieved (with a link to the raw data file), and browsed / searched. It could be extended to handle other features such as data uploads and comments (which would presumably require authentication of some kind). Data is currently returned as JSON.\r\n\r\nI'm not a physicist myself, so I'm totally out of my depth when it comes to the science of these spectra (I'm a bioinformatician in my day job). However, Luc Lajaunie, who is handling the project said that integration between the site and HyperSpy could be cool! Certainly it would be nice to lower the boundaries for deposition and retrieval of data on the archive in any way possible. For users of HyperSpy it could be an opportunity to easily access a large database of spectra for comparison / use.\r\n\r\nLet me know if you guys on the project would be interested in any such integration. Probably a good start would be to have a look at the beta site (I think you can register yourselves, or drop me a mail), then if you're keen we can chat about the scope of any work.\r\n\r\nPhil"},"comment":{"url":"https://api.github.com/repos/hyperspy/hyperspy/issues/comments/76996239","html_url":"https://github.com/hyperspy/hyperspy/issues/475#issuecomment-76996239","issue_url":"https://api.github.com/repos/hyperspy/hyperspy/issues/475","id":76996239,"user":{"login":"francisco-dlp","id":989719,"avatar_url":"https://avatars.githubusercontent.com/u/989719?v=3","gravatar_id":"","url":"https://api.github.com/users/francisco-dlp","html_url":"https://github.com/francisco-dlp","followers_url":"https://api.github.com/users/francisco-dlp/followers","following_url":"https://api.github.com/users/francisco-dlp/following{/other_user}","gists_url":"https://api.github.com/users/francisco-dlp/gists{/gist_id}","starred_url":"https://api.github.com/users/francisco-dlp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/francisco-dlp/subscriptions","organizations_url":"https://api.github.com/users/francisco-dlp/orgs","repos_url":"https://api.github.com/users/francisco-dlp/repos","events_url":"https://api.github.com/users/francisco-dlp/events{/privacy}","received_events_url":"https://api.github.com/users/francisco-dlp/received_events","type":"User","site_admin":false},"created_at":"2015-03-03T17:48:00Z","updated_at":"2015-03-03T17:48:00Z","body":"@ewels, as you see, we were really desperate to have the API :)\r\n\r\nThe current API is working really well for our purposes. Of course, enabling submission of spectra through the API would be the cherry on the cake and we hope that it'll help you gather more spectra for the data base. Actually, I very much like @Gedeonval [compare2DB method](https://groups.google.com/d/msg/hyperspy-devel/rB2BkzO9UTQ/mKUckqqnOHIJ) that suggests to submit the spectrum to the data base if a query returns no spectra. I think that this can become a powerful tool to get more spectra into the EELS Data Base.\r\n\r\nHyperSpy is not GUI based, but @vidartf is working on a GUI for HyperSpy, [HyperSpyUI](https://github.com/vidartf/hyperspyUI). We'll have to discuss what's the best way of implementing spectra submission once the API is ready, but I think that we can make it reasonably easy for the end-user.\r\n\r\nWe're going to release a new version of HyperSpy on the 28th of March and we would like to have this feature in if possible. It's not a problem at all if you decide to change the API in the close future, just let us know in good time so that we can adapt our code to the new version before you remove the current version of the API.\r\n\r\nI have some few comments:\r\n\r\n* It seems that the number of spectra that a single query can return is limited to 10. If that's the case, can we change the maximum limit through the API?\r\n* The metadata in the files doesn't always include all the info available supported by the format. Sometimes the file metadata is inconsistent with the same information in the database. For example, the msa file contains the following title for the [strontium ferrite](http://eelsdb.eu/spectra/strontium-ferrite-2/) spectrum: \"SrFeO3_EELS-Core-Loss_Feldhoff_Armin_240\" and no other metadata.\r\n* Wouldn't it be better to split some of the edges e.g. \"L2,3\" -> \"L2\", \"L3\", \"M4,5\" -> \"M4\", \"M5\". Actually, splitting all the bundled ones, although redundant in many cases, may be a more straightforward approach. Beside, the current nomenclature seems a bit inconsistent e.g. \"L2,3\" \"N45\".\r\n* It seems that the background of some spectra haw been removed, however, I couldn't find the way to specify that this is the case when uploading a spectrum.\r\n* I personally think that it'll be better to store in the database data that is as raw as possible, could this be encourage on the submission page?\r\n* Could filtering by oxidation state be added to the API?\r\n\r\n"}}