ZINC15 access: Difference between revisions

From DISI
Jump to navigation Jump to search
(blah)
 
m (Frodo moved page Levels of ZINC access to ZINC15 access without leaving a redirect: standardization)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Our model allows four levels of access to ZINC 15.  We take up each level in turn, highlighting pros and cons of each. We should try to reformat this as a table if it makes sense.
ZINC15 may be accessed at four levels.  We take up each level in turn, highlighting pros and cons of each.
 
= ZINC web pages =
This is the easiest way to use ZINC.  


= ZINC flatfiles =  
= ZINC flatfiles =  
This is the original form of ZINC, and still the most popular as measured by TB of downloads.
This is the original form of ZINC, and still the most popular as measured by TB of downloads.
* Pros:
* Pros:
** This is the only way to download really large subsets of ZINC.
** Via the [[Tranche Browser]], this is the only pragmatic way to download really large subsets of ZINC.
** Owing to recent improvements in granularity, it is now easier to get exactly what you want, easier to incrementally update.
** Owing to recent improvements in granularity, it is now easier to get what you want, and to incrementally update.
* Cons:
* Cons:
** These files are static and dated and as such can be slightly out of date.
** These files are static and dated and as such can be slightly out of date (but rarely more than a month or two as of Sept 2015)
** You must use the granularity we have set up (tell us if that can be improved)
** You must use the granularity we have set up.


= Webapi =  
= ZINC API =  
This is a NO-SQL . anonymous.  RESTful.
Anonymous, a subset of which is RESTful. Designed for experts to build their own tools.


= ZINCapi =  
= ZINC shell =  
* more flexible.  
* more flexible.  
* allows union, intersection, custom sql, joins.  
* allows union, intersection, custom sql, joins not easily accessed via the API.
* requires lab access (ssh password)  
* requires lab access (ssh)  
 


= Curator =  
= Curator =  
* bottom level acces
* bottom level access
* only used by 2 people currently.  
* only used by 2 people currently.  
* for a private install of ZINC, allows complete control, including modifying tables.
* for a private install of ZINC, allows complete control, including modifying tables.


 
[[Category:ZINC15]]
[[Category:Curator]]
[[Category:ZINCapi]]
[[Category:Webapi]]

Latest revision as of 00:34, 2 October 2015

ZINC15 may be accessed at four levels. We take up each level in turn, highlighting pros and cons of each.

ZINC web pages

This is the easiest way to use ZINC.

ZINC flatfiles

This is the original form of ZINC, and still the most popular as measured by TB of downloads.

  • Pros:
    • Via the Tranche Browser, this is the only pragmatic way to download really large subsets of ZINC.
    • Owing to recent improvements in granularity, it is now easier to get what you want, and to incrementally update.
  • Cons:
    • These files are static and dated and as such can be slightly out of date (but rarely more than a month or two as of Sept 2015)
    • You must use the granularity we have set up.

ZINC API

Anonymous, a subset of which is RESTful. Designed for experts to build their own tools.

ZINC shell

  • more flexible.
  • allows union, intersection, custom sql, joins not easily accessed via the API.
  • requires lab access (ssh)

Curator

  • bottom level access
  • only used by 2 people currently.
  • for a private install of ZINC, allows complete control, including modifying tables.
Retrieved from "http://wiki.docking.org/index.php?title=ZINC15_access&oldid=9164"