Paste number 136457: proposed blog post

Index of paste annotations: 1 | 2

Paste number 136457: proposed blog post
Pasted by: gmcharlt
When:8 years, 2 months ago
Share:Tweet this! | http://paste.lisp.org/+2XAH
Channel:None
Paste contents:
Raw Source | XML | Display As
Title: Olly olly oxen free: users of Evergreen APIs, stand up and be counted

Are you, your product, or your service interacting with Evergreen in some automated fashion?  If so, we’d like to hear from you.

I’m using the phrase “automated fashion” very broadly.  There are many ways to receive data from an Evergreen system, update data in an Evergreen database, or make transactions happen.  A few of these ways include:

XML-RPC calls to invoke Evergreen service methods
SIP2 to perform patron and circulation requests
Z39.50, unAPI, and OpenSearch to retrieve catalog data
MARC exports and imports
Screen-scraping (although if you’re screen-scraping Evergreen, we may be able to suggest a better way to do it)
Interacting with the Evergreen staff client
Direct database access
Some of the things we’d like to know include:

The name of your service or product
What it does for an Evergreen library
How it is accessing Evergreen
Whether there are specific APIs or entry points that your application depends on
Are there things that Evergreen could be doing to make your life easier?
To respond, please comment on this post.  If, for some reason, you need to respond privately, please email info AT evergreen-ils.org.

Annotations for this paste:

Annotation number 1: next draft
Pasted by: gmcharlt
When:8 years, 2 months ago
Share:Tweet this! | http://paste.lisp.org/+2XAH/1
Paste contents:
Raw Source | Display As
Are you, your product, or your service interacting with Evergreen in some automated fashion?  If so, we’d like to hear from you.

I’m using the phrase “automated fashion” very broadly.  There are many ways to receive data from an Evergreen system, update data in an Evergreen database, or make transactions happen.  A few of these ways include:

XML-RPC calls to invoke Evergreen service methods
SIP2 to perform patron and circulation requests
Z39.50, unAPI, and OpenSearch to retrieve catalog data
MARC exports and imports
Screen-scraping (although if you’re screen-scraping Evergreen, we may be able to suggest a better way to do it)
Interacting with the Evergreen staff client
Direct database access

Some of the things we’d like to know include:

The name of your service or product
What it does for an Evergreen library
How it is accessing Evergreen
Whether there are specific APIs or entry points that your application depends on
Are there things that Evergreen could be doing to make your life easier?

Why do we want to know?  Our reasons include:

Finding out which entry points we should be particularly careful about changing as Evergreen gets enhanced.
See if there are things we could be doing better to encourage more people and applications to participate in the Evergreen ecosystem.
(Maybe) putting together a list of third-party services that interact with Evergreen.

To respond, please comment on this post.

Annotation number 2: draft 3
Pasted by: gmcharlt
When:8 years, 2 months ago
Share:Tweet this! | http://paste.lisp.org/+2XAH/2
Paste contents:
Raw Source | Display As
Are you, your product, or your service interacting with Evergreen in some automated fashion?  If so, we’d like to hear from you.

I’m using the phrase “automated fashion” very broadly.  There are many ways to receive data from an Evergreen system, update data in an Evergreen database, or make transactions happen.  A few of these ways include:

XML-RPC calls to invoke Evergreen service methods
SIP2 to perform patron and circulation requests
Z39.50, unAPI, and OpenSearch to retrieve catalog data
MARC exports and imports
Screen-scraping (although if you’re screen-scraping Evergreen, we may be able to suggest a better way to do it)
Interacting with the Evergreen staff client
Direct database access

Some of the things we’d like to know include:

The name of your service or product
What it does for an Evergreen library
How it is accessing Evergreen
Whether there are specific APIs or entry points that your application depends on
Are there things that Evergreen could be doing to make your life easier?

We want to hear from everybody, whether you are a consortium that has integrated Evergreen with other software, an Evergreen support group,  a vendor selling products or services to libraries, or a member of a free software project whose software talks with Evergreen.  If you work for an Evergreen library and know that Evergreen works with another service, we want to hear from you too, even if you don’t know how Evergreen is doing the talking.

Why do we want to know?  Our reasons include:

Finding out which entry points we should be particularly careful about changing as Evergreen gets enhanced.
See if there are things we could be doing better to encourage more people and applications to participate in the Evergreen ecosystem.
(Maybe) putting together a list of third-party services that interact with Evergreen.

To respond, please comment on this post.

Colorize as:
Show Line Numbers

Lisppaste pastes can be made by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively.