Differences

This shows you the differences between two versions of the page.

--- advocacy:replies:2011-10-02-montoya [2011/10/03 09:43] – created dbs
+++ advocacy:replies:2011-10-02-montoya [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 11: / Line 11: @@
 Here are the questions :
-- Will it be possible to Evergreen to allow the user to access comments from
+  - Will it be possible to Evergreen to allow the user to access comments from other readers of other libraries or connected via a social network, during his navigation ?
-other readers of other libraries or connected via a social network, during
+    * Some exploratory work on enabling social features in Evergreen was [[http://markmail.org/message/nb2w7fslmsi33x33|offered to the community]] in October 2010 but that work has not yet been completed.
-his navigation ?
+    * Evergreen supports the integration of the Chilifresh added content service out of the box, which offers an aggregated user-provided comment content to libraries that subscribe to the Chilifresh service.
-- Will Evergreen be able to recommend other records to a reader, depending
+  - Will Evergreen be able to recommend other records to a reader, depending on previous loans of the reader, or based on loans related to other anonymous readers.
-on previous loans of the reader, or based on loans related to other
+    * Evergreen does not offer this feature today; there are no known plans to develop this feature.
-anonymous readers. Will it incorporate FRBR to offer other multimedia
+  - Will it incorporate FRBR to offer other multimedia editions of the work ?
-editions of the work ?
+    * Evergreen has supported a FRBR-like search that offers results that include other editions & multimedia versions of a work since the 1.0 release in 2006.
-- Can Evergreen provide a single interface, fully integrated in the existin=
+  - Can Evergreen provide a single interface, fully integrated in the existing websites, providing search capabilities on the site of the institution and in the databases subscribed (federated search).
-g
+    * Evergreen does not offer all of the features of a complete discovery layer; there are no known plans to develop this feature. Evergreen would prefer to continue to be easy to integrate into a dedicated discovery layer rather than attempting to become a discovery layer and diluting its focus. That said, Evergreen does offer integration with the SFX OpenURL resolver so that the electronic resources & coverage & embargo (if any) available for any ISBN or ISSN are displayed inline with Evergreen's search results.
-websites, providing search capabilities on the site of the institution and
+  - Can Evergreen offer multiple interfaces based on audience profiles to adjust the results and the interface. For example children, or persons with disabilities ?
-in the databases subscribed (federated search).
+    * Yes. The current catalogue interface, in use since Evergreen 1.6, has been tested with a screen reader, and offers the ability to be "skinned" to provide alternate interfaces such as a simplified children's catalogue. Evergreen 2.2 will also offer the [[dev:opac:template-toolkit:release_notes|"TPAC" catalogue interface]], which offers more semantically rich HTML and a user interface that will be visually appealing in modern browsers while able to be navigated in a text browser. The TPAC catalogue interface is also built to be easy to customize.
-- Can Evergreen offer multiple interfaces based on audience profiles to
+    * The [[http://comments.gmane.org/gmane.education.libraries.open-ils.general/5100|kids catalog]] for Evergreen is currently in development.  It will offer a search interface that can be limited to just juvenile materials based on copy location.
-adjust the results and the interface. For example children, or persons with
+  - Shall the ILS's interface be displayed on a mobile device according to ergonomics concerns ? Shall it be carried in a mobile version, and in iOS, Android and - maybe - Meego applications ?
-disabilities ?
+    * The existing catalogue has been tested successfully with iOS and Android browsers; all functions can be carried out on these devices. The TPAC catalogue in 2.2 will offer an improved mobile experience as it uses much less bandwidth and makes fewer HTTP requests.
-- Shall the ILS=92s interface be displayed on a mobile device according to
+  - Can Evergreen provide not only access to records of documents available in the libraries of the network, but also to digital documents in the library, scanned by it, or that it holds the rights via a subscription ?
-ergonomics concerns ? Shall it be carried in a mobile version, and in iOS,
+    * Any resource accessible via an HTTP link can use Evergreen's "located URIs" or the integrated SFX OpenURL resolution to provide access to electronic resources. However, Evergreen does not seek to replace the functionality of an institutional repository / digital repository; the expected workflow would be to scan the digital resource into the institutional repository / digital repository and load a MARC record into Evergreen that points to the repository for that resource.
-Android and - maybe - Meego applications ?
+  - Is Evergreen able to index federate alternative sources of information ? I mean, the indexing of databases must be done ahead to provide a fast response time (I exclude OAI)
-- Can Evergreen provide not only access to records of documents available i=
+    * Evergreen does not seek to become a federated search engine; there are no known plans to develop this feature.
-n
+  - Can Evergreen ensure the supply of native metadata to search engines to allow a useful and effective referencing ?
-the libraries of the network, but also to digital documents in the library,
+    * Yes. Evergreen offers access to bibliographic records (with holdings) and authority records via SRU and Z39.50, as well as a number of APIs that support alternate formats.
-scanned by it, or that it holds the rights via a subscription ?
-- Is Evergreen able to index federate alternative sources of information ? =
-I
-mean, the indexing of databases must be done ahead to provide a fast
-response time (I exclude OAI)
-- Can Evergreen ensure the supply of native metadata to search engines to
-allow a useful and effective referencing ?