27 results found

1. Put useful data into the RSS feeds created by Primo

   Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.

   Let's start with the feed header:

   Primo delivers <rss version="2.0">
   The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
   https://tools.ietf.org/html/rfc4287
   It is simply the better option for may reasons.
   http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

   The description of the feed is <title>Records from Primo</title> .
   As a user I would like to see my search terms in the feed title - like in the brief result screen in the web interface. At minimum it should be the name of the service where this feed is coming from. The name of software used to create the feed is useless to a reader.

   The link to the source is pointing back to the Primo main page with the classic user interface. But that's confusing for institutions using the new user interface!

   Let's have a look to a feed item:

   A cruical element of RSS feeds is the
   <pubDate>Thu, 09 Nov 2017 16:25:22 GMT</pubDate>
   The specification says: "Its value is a date, indicating when the item was published." In a Primo feed this is always the same date; I assume it is the time stamp when the feed was created. Please change this immediately. RSS management software cannot handle it because the pubDate is used for chronological sorting and to find out what's new. What's needed is the publication date of the publication or second best the date and time when the record was added to the Primo index.

   The delivered link in the link field is "the URL of the item". It's pointing back to the full view of the record in Primo. That makes sense. But if available I would like to get the OpenURL here because I want to connect my users to the article or the service page and not to the Primo record again. It's fulfillment at this point!

   Why the same link is also in guid is a mystery to me. RSS standard says: "guid stands for globally unique identifier. It's a string that uniquely identifies the item. When present, an aggregator may choose to use this string to determine if an item is new." What about the PNX ID?

   Last not least the description:
   <description>Plasmodium Falciparum -- Analysis ; Proteases -- Analysis ; Proteins -- Analysis ; Phosphates -- Analysis ; Malaria -- Analysis;</description>
   Often it incorporates only "N/A" or sometimes subject headings. But the description should include the same information as the brief view in the web interface of Primo like bibliographic information, identifier, subject headings, language, etc. This is what the user will see in his feed reader of choice or what a feed aggregation system can use to give meaningful context for the title of this item. Of course it's tricky because a Primo search delivers very different types of content with very different metadata. Books have authors; journals have not. Articles are published in a journal and pictures have a resolution and digital objects have a file format.

   Today there are no customization options for the feed content. If the settings of the brief view are applied to the feed too, it would improve the item description massively and solve the description problem. This need is solved for the export to a reference management software. The RSS feed for a query is not so much different from that.

   Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.

   Let's start with the feed header:

   Primo delivers <rss version="2.0">
   The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
   https://tools.ietf.org/html/rfc4287
   It is simply the better option for may reasons.
   http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

   The description of the feed is <title>Records from Primo</title> .
   As a user I would like to see my search terms in the feed title - like in… more

   55 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Allow for consistant customizations in the new UI

   The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
   This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
   We want to implement extensions for functionalities like:
   • Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off campus, browser version used, search query, pnx-id,.. and his e-mail address when he is signed in. Our e-resources staff finds this functionality extremely useful: more linking issues are reported now and they can be handled in a more efficient way.
   • Offer a button “Pay fines” that allows a user to pay fines online. The button is only displayed when the user has fines.

   These are extensions that we currently implemented in our old UI.
   But creating extensions that make use of session data (like user email, vid, …) are time consuming and risk full:
   • Time consuming because documentation is limited not to say non-existing, this requires reading the code. It has a high maintenance cost since after every release, extensions can break and it is difficult to find out why because of the lack of clear release notes.
   • It is risk full because we don’t know whether we will be able to fix the functionality in the two weeks between release on staging and production. It is also risk full because we don’t know if the extensions will still work after the transition to Angular 2.

   Our request is :
   Please provide us with session data in every component so we can quickly create components.
   One way to make the extensions manageable and future proof, is to use a data model (see primo-explore-dom). If the data is framework agnostic it will become more portable and working with data is easier and almost timeless.
   This way everybody can develop within the reach of their skillset and more institutions would be able to take profit of the open discovery framework.
   But we are open to any solution to overcome the issues mentioned.

   The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
   This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
   We want to implement extensions for functionalities like:
   • Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off… more

   205 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Create link for patron to report issue with Primo Central Record

   This idea comes from a ticket submitted by a professor last week regarding a journal article resource that was marked as "peer reviewed" in PCI incorrectly. She reported it to us and we reported it to ExLibris, but it would seem more efficient to include a link that could report the problem directly to ExLibris for PCI content. I imagine something similar to the "report an issue" link found in google books: https://www.screencast.com/t/BdLZo2tR6D

   55 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   10 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. • Records without a date at the bottom of results list when sorting on date oldest

   At this moment, the sort option “Date oldest” displays the records without a date on top of the results list. This is confusing and not relevant for users; when there are several records without a Creation Date they probably conclude that sorting on date oldest doesn’t work. Our request is to display the records without a date always at the bottom of the results list when a sort option on date is used (thus as well for date oldest as for date newest)

   79 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   Hi all,

   This is to update that this is currently not planned to be developed. We might evaluate it again in the future.

   Therefore we are removing the "Under review" status for now.

   Best regards,

   Yael.

5. Real Time Availability for Electronic Resources

   If a resource from Alma is unavailable to a end user due to a campus or IP restriction and receives the "No Full Text available" message, then update the "Online Access" green dot to "No Full Text/Red Dot" or "Sign In for access options/ Yellow dot"

   •  

   111 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Full integration of Syndetics enrichment content

   Syndetic Solutions enrichment content should be indexed in Primo, to aid the retrieval of books (especially by chapter titles in TOCs) and displayed inline in the new Primo UI. The acquisition of Ex Libris by Proquest should make this commercially easier to arrange, and it should be technically easier on the Primo "cloud" platform.

   204 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Adding 'Issue' as a new resource type in Primo Central

   Resource types used in Primo Central are limited to 23 (book, article, journal, image...) [See pdf "Primo Central Index Resource Types" in the Documentation Center].

   For digitized journal issues, the type in use is 'journal'. Archive collections like HathiTrust may contain tens of thousands of digitized journal issues; institutional repositories may also contain complete issues… This is finally confusing for end-users for who see issues labelled as journals and for whom filtering by resource type has become useless.

   Adding a 24th type 'Issue' for this material would be welcome! ‘Journal’ would thus only remain for real journal records.

   93 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Under Review  ·  8 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating