24 results found

1. Support CDATA sections (as used by SharePoint and Drupal) in Events PI RSS

   The RSS for the Events PI often contains HTML characters in the <description> that have to be escaped somehow to be considered valid XML. The Events PI has a toggle switch to indicate whether it should expect HTML in the description element.

   Either individual HTML characters can be replaced with entity references e.g. < replaced by & lt ; and > replaced by & gt ; or alternatively you can enclose the HTML in a CDATA section e.g. <![CDATA[ <b>Our event!</b> ]]>.

   Both SharePoint and Drupal use CDATA sections to enclose HTML in the RSS views they generate by default, rather than escaping the individual characters, which seems more efficient and is definitely valid XML. Unfortunately the Events PI will literally display the HTML code if the RSS includes CDATA sections leading to the somewhat unfortunate HTML 'rich' events as seen in the example attachment. The only work around is to intercept and transform the HTML before it is ingested by the Events PI, which is yet another thing to maintain.

   Ex Libris Support asked me to raise this feature request as support for CDATA is not currently planned, but given that big platforms generate RSS in this format it seems to me like it would be a 'good thing', and arguably what one might expect to happen anyway. Thanks in advance for the up votes!

   The RSS for the Events PI often contains HTML characters in the <description> that have to be escaped somehow to be considered valid XML. The Events PI has a toggle switch to indicate whether it should expect HTML in the description element.

   Either individual HTML characters can be replaced with entity references e.g. < replaced by & lt ; and > replaced by & gt ; or alternatively you can enclose the HTML in a CDATA section e.g. <![CDATA[ <b>Our event!</b> ]]>.

   Both SharePoint and Drupal use CDATA sections to enclose HTML in the RSS views they generate by default,… more

   •  

   1 vote

   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…)
   0 comments  ·  Integrations  ·  Edit…  ·  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

2. Grades Product integration

   Oracle PeopleSoft Grades Product Integration:
   We request that the Grades PI for Oracle PeopleSoft is enhanced as follows:
   1. In App Manager > Product Integrations > Grades Instance configuration page, under API Configuration:
   - Below the URL to retrieve the information field, add two additional fields for the entering the two query names (allowing institutions to apply their standard naming conventions for their two queries) and then use/declare these institutional query names as variables in the solution code to replace the default names.
   2. Provide an additional Test API Connection facility, or extend the existing test facility, to enable us to test the second API from the configuration page so that one can test whether it is working and provide a way to troubleshoot it if it is not.
   3. Consider creating a Grades PI that uses one query with two or more variables which are declared as was done with timetables API.
   
   4. If none of the above are feasible, improve the Grades PI guide to be more explicit in its instructions, making it clear that one has to use the default naming convention for the two query names (which is contrary to best practice), and clarifying how the second query associates the terms called in the first query against a specific user ID to the second query calling grades against terms (if only the term parameter is used, as it stands in the documentation, then it will call all grades, not those associated only to a user ID).

   Motivation/justification for these requested changes:
   • Change request 1: This change will allow a broader number of institutions using PeopleSoft to adopt this Grades PI without contravening their PeopleSoft API naming policy.
   
   • Change request 2: This would provide a facility to fully test the Grades PI queries, as is provided in the other product integrations.
   
   • Change request 3: This is more of a request to investigate simplifying the grades PI, if there was one query to test, then change request 1 and 2 additional fields and test facility would not be required, as the query name could be referenced in the URL to retrieve the information).
   
   • Change request 4: We wasted a lot of time trying unsuccessfully to get this query to work (using our own unique query names, which is the standard practice), when we were told one has to use the exact query names specified in the examples. If the documentation is more explicit, it would save organisations a lot of time in getting this query to work. Also indicating what needs to be entered in what fields would also be useful. Since this works differently to other PeopleSoft queries we have used as it is more hard coded and locked down.

   Oracle PeopleSoft Grades Product Integration:
   We request that the Grades PI for Oracle PeopleSoft is enhanced as follows:
   1. In App Manager > Product Integrations > Grades Instance configuration page, under API Configuration:
   - Below the URL to retrieve the information field, add two additional fields for the entering the two query names (allowing institutions to apply their standard naming conventions for their two queries) and then use/declare these institutional query names as variables in the solution code to replace the default names.
   2. Provide an additional Test API Connection facility, or extend the existing test facility, to enable us… more

   1 vote

   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…)
   0 comments  ·  Integrations  ·  Edit…  ·  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

3. Bus tracking

   The bus tracking integration looks like it could really benefit our users but just being limited to one provider is limiting. If the module could be opened up to a RESTFul API - this would mean we could then use the module but with different providers.

   Sort of linked to the now closed ticket of #17667385

   https://knowledge.exlibrisgroup.com/campusM/Product_Documentation/Managing_Product_Integrations/Bus_Tracking

   1 vote

   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…)
   0 comments  ·  Integrations  ·  Edit…  ·  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

4. Add voice search
   1 vote

   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…)
   0 comments  ·  Integrations  ·  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