<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Fri Feb 09 00:06:09 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[UXPROD-148] Allow the integration of multiple knowledgebases for e.g. reference cataloging. Some will support holdings such as EPKB.</title>
                <link>https://folio-org.atlassian.net/browse/UXPROD-148</link>
                <project id="10000" key="UXPROD">UX Product</project>
                    <description>&lt;p&gt;This feature was created before the ERM subgroup was formed. This may eventually become a feature or set of stories related to  &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-589&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;589&lt;/a&gt;&lt;br/&gt;
---------------------------------------------------------&lt;br/&gt;
Allow the integration of multiple knowledgebases for e.g. reference cataloging.&#65533; Some will support holdings such as EPKB. &lt;/p&gt;

&lt;p&gt;Do we have any plans for expanding the Codex Search beyond the present two sources (Inventory and EBSCO KB), eg. GoKB for v1? We need to avoid allowing the design and specifiction of the Codex to be too dominated by the two sources we happen to have right now. If we can add a at least one more source, then the use case for Codex Search will be more evident for SMEs and testers, and we can ensure both the UX and implementation won&apos;t get any surprises down the line.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10303">UXPROD-148</key>
            <summary>Allow the integration of multiple knowledgebases for e.g. reference cataloging. Some will support holdings such as EPKB.</summary>
                <type id="10002" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium">New Feature</type>
                            <parent id="10561">UXPROD-833</parent>
                                    <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Won&apos;t Do</resolution>
                                                        <assignee accountid="557058:f80403de-e149-421e-8750-af45c853402f">Charlotte Whitt</assignee>
                                                                <reporter accountid="5af5ed55244bc90a106063c7">Cate Boerema</reporter>
                                    <labels>
                            <label>crossrmapps</label>
                            <label>erm</label>
                            <label>metadatamanagement</label>
                    </labels>
                <created>Thu, 18 Jan 2018 22:48:52 +0000</created>
                <updated>Wed, 16 Sep 2020 21:12:50 +0000</updated>
                            <resolved>Tue, 9 Apr 2019 10:28:44 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                <comments>
                                                            <comment id="11093" author="5bffed52a1b46046f530c8f7" created="Fri, 2 Mar 2018 16:18:34 +0000"  >&lt;p&gt;I am 100% on board with &quot;We need to avoid allowing the design and specification of the Codex to be too dominated by the two sources we happen to have right now. If we can add a at least one more source, then the use case for Codex Search will be more evident for SMEs and testers, and we can ensure both the UX and implementation won&apos;t get any surprises down the line.&quot;&lt;/p&gt;

&lt;p&gt;But my understanding &lt;em&gt;had&lt;/em&gt; been that we were not planning to do this for v1. If we did so it, it would be a non-trivial bit of work, involving new UX elements and their implementation down the stack through stripes-components, stripes-smart-components and ui-users. But I think it&apos;s important work.&lt;/p&gt;

&lt;p&gt;Also, the back-end component would be entirely dependent on what the additional resource (or resources) to be integrated was.&lt;/p&gt;</comment>
                                                            <comment id="11099" author="5bffed52a1b46046f530c8f7" created="Fri, 2 Mar 2018 16:24:46 +0000"  >&lt;p&gt;On the UI side, the complication is that having two Codex sources of the same kind (&quot;KB&quot;) introduces a new notion into the mix, and we&apos;d need UX work, which would then of course need to be realised in the UI. Would we want the ability to select &quot;all sources of type KB&quot;, for example?&lt;/p&gt;

&lt;p&gt;If not &amp;#8211; if we just treat it as an opaque third source, with no classification of sources &amp;#8211; then it&apos;s much simpler to handle.&lt;/p&gt;</comment>
                                                            <comment id="11103" author="5af5ed55244bc90a106063c7" created="Wed, 4 Apr 2018 12:01:05 +0000"  >&lt;p&gt;I think &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt; seems like the natural PO for this feature.  Owen, if that doesn&apos;t make sense, let me know.&lt;/p&gt;</comment>
                                                            <comment id="11109" author="62a96ae7192edb006f9f1bf9" created="Wed, 30 May 2018 13:00:10 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt;  - I think we should discuss how the work done for mod-kb-ebsco ties into this effort. And also my only concern with codex at this time is there is no way to search for packages and it does not provide any titles in the context of a package. &lt;/p&gt;</comment>
                                                            <comment id="11112" author="5bffed52a1b46046f530c8f7" created="Wed, 30 May 2018 13:06:52 +0000"  >&lt;p&gt;As I understand it, the absence of support for packages is not limited to the Codex, but comes from the fact that they are not recognised in Inventory either &amp;#8211; isn&apos;t that right? If so, then there&apos;s probably not much point putting too much effort into them on the Codex side before that&apos;s fixed.&lt;/p&gt;</comment>
                                                            <comment id="11117" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 30 May 2018 17:58:08 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; - Packages in Inventory is definitely considered &lt;img class=&quot;emoticon&quot; src=&quot;/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt; A small working group with participants from MM-SIG and RM-SIG is established around this work. First meeting is expected to happen next week - see: &lt;a href=&quot;https://wiki.folio.org/pages/resumedraft.action?draftId=14452087&amp;amp;draftShareId=0a8491a2-dcf4-4e48-b26d-b38b1e88c584&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://wiki.folio.org/pages/resumedraft.action?draftId=14452087&amp;amp;draftShareId=0a8491a2-dcf4-4e48-b26d-b38b1e88c584&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="11121" author="5af5ed55244bc90a106063c7" created="Sun, 10 Jun 2018 14:25:57 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt;, I know that as part of your ERM project you will be working to integrate GoKB.  Given that, I would like to keep this old feature with your work.  Not sure where it belongs specifically so I just put it with Agreements (
    &lt;span class=&quot;jira-issue-macro&quot; data-jira-key=&quot;UXPROD-573&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-573&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Agreements&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/images/icons/issuetypes/epic.svg&quot; /&gt;
            UXPROD-573
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-current jira-macro-single-issue-export-pdf&quot;&gt;In Progress&lt;/span&gt;
            &lt;/span&gt;
) for now.&lt;/p&gt;</comment>
                                                            <comment id="11125" author="557058:a957226f-df85-4fc8-97f4-8b27a26029ed" created="Wed, 20 Jun 2018 13:02:51 +0000"  >&lt;p&gt;In the gap analysis Chicago indicated that they need this feature within the first quarter of their &quot;go live&quot; date:&lt;br/&gt;
&quot;Integration with Ex Libris KBs: SFX and 360 knowledge base, and all of the functionality available currently for EBSCO KB.&lt;br/&gt;
Work would be dependent upon legal agreement of Ex Libris.&quot;&lt;/p&gt;</comment>
                                                            <comment id="11129" author="557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa" created="Wed, 20 Jun 2018 13:22:00 +0000"  >&lt;p&gt;&quot;all of the functionality available currently for EBSCO KB&quot; would be an eHoldings question I think &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62a96ae7192edb006f9f1bf9&quot; class=&quot;user-hover&quot; rel=&quot;62a96ae7192edb006f9f1bf9&quot; data-account-id=&quot;62a96ae7192edb006f9f1bf9&quot; accountid=&quot;62a96ae7192edb006f9f1bf9&quot; rel=&quot;noreferrer&quot;&gt;Khalilah Gambrell&lt;/a&gt;&lt;br/&gt;
That&apos;s not to say it is out of scope for ERM to work with these KB it&apos;s just in terms of how this is phrased makes me think that what they are looking for is the eHoldings functionality right now?&lt;/p&gt;</comment>
                                                            <comment id="11134" author="62a96ae7192edb006f9f1bf9" created="Wed, 20 Jun 2018 17:24:23 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Aa957226f-df85-4fc8-97f4-8b27a26029ed&quot; class=&quot;user-hover&quot; rel=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; data-account-id=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; accountid=&quot;557058:a957226f-df85-4fc8-97f4-8b27a26029ed&quot; rel=&quot;noreferrer&quot;&gt;Holly Mistlebauer&lt;/a&gt; -  My guess is Charlotte outlined this feature to support the Codex. There is another feature that pertains to integration of KB providers to support eholdings and ERM (&lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-166&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-166&lt;/a&gt;). It might be helpful to breakdown the feature into multiple features represent integration per KB provider for prioritization&lt;/p&gt;</comment>
                                                            <comment id="11139" author="5af5ed55244bc90a106063c7" created="Wed, 25 Jul 2018 10:07:48 +0000"  >&lt;p&gt;Per discussion with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt;, the ERM features will interact with multiple KBs (GOKb and EPKB to start), but that capability is included in the (other) ERM features Owen created.  &lt;/p&gt;

&lt;p&gt;This feature was originally created by Charlotte (perhaps based on something in the v1 roadmap).  &lt;/p&gt;

&lt;p&gt;Based on the description here and the people who estimated it (&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; and &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A28cce430-5ccd-47e7-88fe-1b26c20ee795&quot; class=&quot;user-hover&quot; rel=&quot;557058:28cce430-5ccd-47e7-88fe-1b26c20ee795&quot; data-account-id=&quot;557058:28cce430-5ccd-47e7-88fe-1b26c20ee795&quot; accountid=&quot;557058:28cce430-5ccd-47e7-88fe-1b26c20ee795&quot; rel=&quot;noreferrer&quot;&gt;Ian Ibbotson (Use this one)&lt;/a&gt;), &lt;em&gt;this&lt;/em&gt; feature seems to be about incorporating GoKB into the Codex app.  This is a worthwhile endeavor, but not in scope for Owen.  &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, I am turning this back over to you and putting in the Codex epic.  I am also renaming this, as the current feature name (Allow the integration of multiple knowledgebases for e.g. reference cataloging. Some will support holdings such as EPKB) is confusing.  &lt;/p&gt;

&lt;p&gt;If I am misunderstanding the intended purpose of this feature, please let me know.  I don&apos;t want to change the name of the feature in such a way that it no longer represents what was estimated.  Thanks!&lt;/p&gt;</comment>
                                                            <comment id="11146" author="5af5ed55244bc90a106063c7" created="Wed, 25 Jul 2018 10:10:51 +0000"  >&lt;p&gt;If everyone is okay with the changes I&apos;ve made to the title and epic of this issue, I think the next step is to follow up with Chalmers to see if they really need GOKb integrated into the Codex for go-live if it will be integrated into ERM.&lt;/p&gt;</comment>
                                                            <comment id="11150" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 25 Jul 2018 11:22:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt; - okay. I&apos;ll reach out to Chalmers. Both Theodor and Lisa is away on vacation this week. But as soon one of them are back, I&apos;ll talk to them about Chalmers expectations.&lt;/p&gt;</comment>
                                                            <comment id="11154" author="5bffed52a1b46046f530c8f7" created="Wed, 25 Jul 2018 11:24:35 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ed55244bc90a106063c7&quot; class=&quot;user-hover&quot; rel=&quot;5af5ed55244bc90a106063c7&quot; data-account-id=&quot;5af5ed55244bc90a106063c7&quot; accountid=&quot;5af5ed55244bc90a106063c7&quot; rel=&quot;noreferrer&quot;&gt;Cate Boerema&lt;/a&gt;, you wrote &quot;(GOKb and EPKB to start)&quot;. Is EPKB the same thing as the ESSCO KB we&apos;ve been using up till now (and usually abbreviating EKB)?&lt;/p&gt;</comment>
                                                            <comment id="11159" author="62a96ae7192edb006f9f1bf9" created="Wed, 25 Jul 2018 11:27:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5bffed52a1b46046f530c8f7&quot; class=&quot;user-hover&quot; rel=&quot;5bffed52a1b46046f530c8f7&quot; data-account-id=&quot;5bffed52a1b46046f530c8f7&quot; accountid=&quot;5bffed52a1b46046f530c8f7&quot; rel=&quot;noreferrer&quot;&gt;Mike Taylor&lt;/a&gt; - Yes EPKB is the same as EBSCO KB. We should probably stick with EBSCO KB for Folio purposes. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af80403de-e149-421e-8750-af45c853402f&quot; class=&quot;user-hover&quot; rel=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; data-account-id=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; accountid=&quot;557058:f80403de-e149-421e-8750-af45c853402f&quot; rel=&quot;noreferrer&quot;&gt;Charlotte Whitt&lt;/a&gt;, I scheduled a meeting with Theodor for 7/31. Do you want to be a part of that meeting? &lt;/p&gt;</comment>
                                                            <comment id="11164" author="5af5ed55244bc90a106063c7" created="Wed, 25 Jul 2018 12:14:39 +0000"  >&lt;p&gt;Sorry - will use &quot;EBSCO KB&quot; from now on!&lt;/p&gt;</comment>
                                                            <comment id="11167" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Wed, 25 Jul 2018 12:29:34 +0000"  >&lt;p&gt;&amp;gt; I scheduled a meeting with Theodor for 7/31. Do you want to be a part of that meeting?&lt;br/&gt;
Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=62a96ae7192edb006f9f1bf9&quot; class=&quot;user-hover&quot; rel=&quot;62a96ae7192edb006f9f1bf9&quot; data-account-id=&quot;62a96ae7192edb006f9f1bf9&quot; accountid=&quot;62a96ae7192edb006f9f1bf9&quot; rel=&quot;noreferrer&quot;&gt;Khalilah Gambrell&lt;/a&gt;, yes that would be great. Thanks&lt;/p&gt;</comment>
                                                            <comment id="11171" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Tue, 31 Jul 2018 14:24:54 +0000"  >&lt;p&gt;Follow-up: &lt;br/&gt;
Chalmers expectation is that EBSCO KB is integrated in Codex. &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A0a02d059-b8b9-48b3-8a58-727ec44d05d2&quot; class=&quot;user-hover&quot; rel=&quot;712020:0a02d059-b8b9-48b3-8a58-727ec44d05d2&quot; data-account-id=&quot;712020:0a02d059-b8b9-48b3-8a58-727ec44d05d2&quot; accountid=&quot;712020:0a02d059-b8b9-48b3-8a58-727ec44d05d2&quot; rel=&quot;noreferrer&quot;&gt;Theodor Tolstoy (One-Group.se)&lt;/a&gt; confirmed that it would be okay with Chalmers that the integration of GOKb into Codex, can wait  with 1 year. I&apos;ll change the ranking accordingly.&lt;/p&gt;</comment>
                                                            <comment id="11177" author="557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa" created="Fri, 25 Jan 2019 14:30:05 +0000"  >&lt;p&gt;My feeling is that we&#8217;ve now gone past this in terms of the ERM work, and that as a feature it is probably a bit broad to be useful going forward - as we probably want to look at integration of specific knowledgebases rather than just generally allow for integration&lt;/p&gt;

&lt;p&gt;We already have:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-589&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-589&lt;/a&gt; (GOKb integration)&lt;br/&gt;
&lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-1465&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://folio-org.atlassian.net/browse/UXPROD-1465&lt;/a&gt; (KBART integration)&lt;/p&gt;

&lt;p&gt;as well as work under way to ensure eHoldings title-packages or packages can relate to Agreements, Licenses, POLs etc.&lt;/p&gt;

&lt;p&gt;Unless there are objections I&apos;ll close this as &quot;won&apos;t do&quot; with a comment that we need to describe specific integrations where required&lt;/p&gt;</comment>
                                                            <comment id="11184" author="557058:f80403de-e149-421e-8750-af45c853402f" created="Fri, 25 Jan 2019 14:44:02 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt; - as we discussed on Slack, this UXPROD is from the original roadmap spreadsheet by &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt;, and the ERM work has moved in a new direction, and things have changed since the initial roadmap was defined. &lt;br/&gt;
I definitely support what you suggest in the comment above. So please go ahead and close this 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-148&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-148&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Allow the integration of multiple knowledgebases for e.g. reference cataloging. Some will support holdings such as EPKB.&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-148
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                                                            <comment id="11189" author="5af5ecdb772036612ff61cf1" created="Fri, 25 Jan 2019 15:07:28 +0000"  >&lt;p&gt;IS the assumption that the eHoldings app can handle KBs outside of GOKb for libraries that want a direct connection to KB data?  This is specifically about references and not copying or importing records which is very different from 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UXPROD-589&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UXPROD-589&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Import and synchronise resources from GOKb&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10322?size=medium&quot; /&gt;
            UXPROD-589
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 &amp;amp; 1465.  &lt;br/&gt;
I would just remove the &quot;ERM&quot; tag since that has come to represent the GVB/OLE effort.  I would not close it as there will still be work ongoing in this area.&lt;/p&gt;</comment>
                                                            <comment id="11193" author="557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa" created="Fri, 25 Jan 2019 16:01:02 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5af5ecdb772036612ff61cf1&quot; class=&quot;user-hover&quot; rel=&quot;5af5ecdb772036612ff61cf1&quot; data-account-id=&quot;5af5ecdb772036612ff61cf1&quot; accountid=&quot;5af5ecdb772036612ff61cf1&quot; rel=&quot;noreferrer&quot;&gt;Hkaplanian&lt;/a&gt; the assumption is that eHoldings app can handle KBs that support the necessary API(s) to interact with eHoldings. &lt;/p&gt;

&lt;p&gt;In terms of the rankings from early adopters presumably they are looking for specific integrations rather than a general ability? Wouldn&apos;t expressing those requirements give us a clearer set of priorities to work towards?&lt;/p&gt;

&lt;p&gt;I&apos;m just not clear on the value of having this open as an issue - how will we know when it is complete?&lt;/p&gt;
</comment>
                                                            <comment id="11199" author="5af5ecdb772036612ff61cf1" created="Fri, 25 Jan 2019 16:11:28 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3Af42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; class=&quot;user-hover&quot; rel=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; data-account-id=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; accountid=&quot;557058:f42d9c43-226d-4aa3-bb31-9b2dd07920aa&quot; rel=&quot;noreferrer&quot;&gt;Owen Stephens&lt;/a&gt;, I can live with that.  Lets close it.&lt;/p&gt;</comment>
                                                            <comment id="11204" author="5af5ed55244bc90a106063c7" created="Fri, 22 Mar 2019 14:09:07 +0000"  >&lt;p&gt;Removing all but the essential features from the Q2 2019 Core Functional team backlog.  After we&apos;ve run the estimates through the cap plan, we may find we can pull in more.&lt;/p&gt;</comment>
                                                            <comment id="11208" author="5af5ed55244bc90a106063c7" created="Tue, 9 Apr 2019 10:28:44 +0000"  >&lt;p&gt;Switching the resolution from done to won&apos;t do so this doesn&apos;t clutter up our reports. See comments from Owen and Harry above for why this issue was closed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="10561">UXPROD-833</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="10574">UXPROD-920</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                    <customfield id="customfield_10048" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Analysis Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10088"><![CDATA[Medium < 5 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10049" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Analysis Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:f80403de-e149-421e-8750-af45c853402f</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Back End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10122"><![CDATA[Large < 10 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10054" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Back End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>557058:28cce430-5ccd-47e7-88fe-1b26c20ee795</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10171"><![CDATA[Prokopovych]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10014" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue key="$xmlutils.escape($text)">Codex</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10050" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front End Estimate</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10098"><![CDATA[Large < 10 days]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10051" key="com.atlassian.jira.plugin.system.customfieldtypes:userpicker">
                        <customfieldname>Front End Estimator</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5bffed52a1b46046f530c8f7</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Front-End Confidence factor</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10107"><![CDATA[Low]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzy8fb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10071" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: 5Colleges (Full Jul 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10223"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10067" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chalmers (Impl Aut 2019)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10206"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10068" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Chicago (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10211"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10069" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Cornell (Full Sum 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10216"><![CDATA[R4]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10074" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: GBV (MVP Sum 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10238"><![CDATA[R1]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10078" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: Lehigh (MVP Summer 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10260"><![CDATA[R3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10089" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: TAMU (MVP Jan 2021)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10315"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10091" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Rank: U of AL (MVP Oct 2020)</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10325"><![CDATA[R2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 2 Mar 2018 16:18:34 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>