Hi Chris,
you were faster than me, I had only written two sentences of a possible email yet ;-)
Yes, please send this text to Sharon Wiles-Young and Holly.
Maybe we should add that these two issues are essential (or critical) for migration and testing.
Best,
Ingolf
Dr. Ingolf Kuss
hbz - Hochschulbibliothekszentrum NRW
Postfach 270451
50510 Köln
Germany
Tel.: (+49) (0) 221 400 75-161
------------------------------------------
I'm happy to reach out to Holly and Sharon Wiles-Young. Would this capture our concerns adequately?
Dear Sharon and Holly,
Two issues came up in our discussions during the SysOp SIG meeting this week that we felt should get a bit of air time in the upcoming developer meeting. In the absense of a product owner for this area, we wanted
to put these ideas in front of you in hopes that they can make their way in front of the right set of developers before the Madrid meeting. Perhaps these issues have already been explored/addressed, but if not it seemed like a good time to get them out there.
1) Consistency of API interfaces: The question was raised in the SysOps SIG as to whether is any attention being paid to making the batch/bulk API interfaces consistent in their interfaces and conventions. There's
a good bit of effort in making the UI consistent across apps, and while it may not be as critical to make back-end APIs be consistent across, apps, this is one place where it seemed like it would be worth checking. If the right folks are thinking about it
early enough in the process, it shouldn't be that difficult to have the batch/bulk interfaces behave in similar ways.
2) Concerns about the use of UUIDs for primary keys as it pertains to migrations: Currently, our existing ILS systems generally use numeric primary keys for data tables. As such, we can refer to bib records,
patron records, etc. by their numeric IDs fairly reasonably. Linkages between records similarly rely on those keys. With FOLIO's use of UUIDs as the primary key, there is going to be a challenge in migration because we won't be able to rely on re-use of
those keys as we migrate our data in. When looking at isolated records, it's not a huge deal. For example, we could put the Voyager BibID into a field in a metadata record, and be able to refer to it. But when we need to migrate in the holdings and items
that are related to that bib, we need to be able to link the records together properly and we wouldn't be able to use that BibID. There is an issue of maintaining the referential integrity of the dataset that, while not insurmountable, is made much, much
more complex (and potentially error-prone) by the change in primary key.
--
Christopher Manly
Director of Library Systems
CU Library Information Technologies
607-255-3344
On January 12, 2018 at 11:51:43 AM, Chris Creswell (
ccc2@lehigh.edu) wrote:
I think it's a good idea to send an e-mail to both Sharon (probably Wiles-Young at Lehigh) and Holly about API consistency and UUID usage for primary keys, and sooner rather than later.
-Chris
On 01/12/2018 10:03 AM, Ingolf Kuss wrote:
Hi all,
Please read the action items at the bottom of the page.
The last action item is particulaly urgent. I think it will be a little late if we ask Holly or Sharon (which one of the two Sharons?) only after next Thursday's meeting to present the two SysOps issues in Madrid. Shouldn't I send one of these persons
an email today or on Monday and ask her if she can present the issues (or delegate the presentation) ? What do you think about this ? The final list with the issues might be handed over to that person later (on Thursday). What about asking Holly now ?
Best,
Ingolf
Dr. Ingolf Kuss
hbz - Hochschulbibliothekszentrum NRW
Postfach 270451
50510 Köln
Germany
Tel.: (+49) (0) 221 400 75-161
------------------------------------------
------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"sysops-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://archives.simplelists.com.
To post to this group, send email to
sysops-sig@ole-lists.openlibraryfoundation.org
<mailto:sysops-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.
--
Christopher Creswell
Library and Technology Services
Sr. Library Systems Analyst
(610) 758-1432
ccc2@lehigh.edu
------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"sysops-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://archives.simplelists.com.
To post to this group, send email to
sysops-sig@ole-lists.openlibraryfoundation.org
<mailto:sysops-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.
------------------------------------------------------
You received this message because you are subscribed to OLE Mailing List
"sysops-sig".
To unsubscribe from this list and stop receiving emails from it, follow
this link: http://archives.simplelists.com.
To post to this group, send email to
sysops-sig@ole-lists.openlibraryfoundation.org
<mailto:sysops-sig@ole-lists.openlibraryfoundation.org>.
Visit this group at
https://ole-lists.openlibraryfoundation.org<https://ole-lists.openlibraryfoundation.org>
.