Forgot password? | Forgot username? | Register

GUID Support Discussion

GUID Support Discussion

A Globally Unique Identifier (GUID) is a persistent unique reference number used as an identifier in computer software.
This forum is for EMu User Community discussion of an EMu development proposal for GUID support.
This EMu development proposal builds on a discussion document drafted in late July 2013 by Larry Gall from the Yale Peabody Museum of Natural History.
Larry’s discussions with a number of EMu institutions, primarily in North America, established a broad consensus for GUID support in EMu modules.
In recent years, KE Software has also had discussions with various EMu customers regarding potential GUID support in EMu.

Attached to this post are Larry Gall's initial discussion document and a KE Software proposal from GUID support within EMu (International and US English versions of the documents are provided).
KE Software invites comment from the EMu User Community.

KE would appreciate if comments could be made by 30 September 2013.

Thanks




Attachments:

2013-07-26-Larry-Gall-YPMNH-GUID.doc

KE-EMu-GUID-Support-IE-20130906-v095.pdf

KE-EMu-GUID-Support-US-20130906-v095.pdf

Gerard Wood (Axiell Melbourne)
useravatar
Offline
61 Posts
Male  Website 
Administrator has disabled public posting. Please login or register in order to proceed.

Re: GUID Support Discussion

Hi Gerard,

Thank you for presenting this proposal and initiating a discussion.  A few questions:

My understanding from the proposal is that only the UUID Version 4 format generator will be provided at no cost; any other formats (as those listed on page 9) will require each institution to pay for customization to set up.  Would you confirm/clarify? 

Will the GUID generation funcationality be configured on a module-by-module basis (in other words, we could turn it on for Catalogue only)?

Within a module, would it be possible to generate one format of GUID for some records, and another format for others?  I'm thinking of biological vs. archives records, etc.

Also, if GUID generation functionality was turned on for a module, would it still be possible for us to populate additional GUIDs via import?

Regards,
Heather

Heather Thorwald
Denver Museum of Nature & Science

Heather Thorwald
Registrar
useravatar
Offline
6 Posts
Website 
Administrator has disabled public posting. Please login or register in order to proceed.

Re: GUID Support Discussion

Hi Heather,

Thanks for your feedback.
I have responded to each of your questions in turn.

My understanding from the proposal is that only the UUID Version 4 format generator will be provided at no cost; any other formats (as those listed on page 9) will require each institution to pay for customization to set up.  Would you confirm/clarify?

In this initial stage only automatic GUID generation in UUID Version 4 format will be included at no cost to customers. However we expect EMu customers will push KE to provide automatic generation for other GUID formats. As is often the case with standards there are numerous other GUID format possibilities. If support for another GUID format (or formats) gains broad consensus in the EMu community, KE would certainly consider embracing that development at no cost to EMu customers. If automatic generation of a particular GUID format has applicability for a small number of customers then that is more of a case for customer funded development. It is possible that some of the larger EMu customers will fund development for automatic generation in a GUID format used in their institution. Once support for automatic generation in a particular GUID format is incorporated into the EMu code base (whether funded by KE or by customers) then it would become available to all customers. KE has been very fortunate that many institutions in the EMu community have a civic minded approach to funding projects. They fund specific developments desired by their institution whilst knowing they are often funding new functionality potentially of use for the broader EMu community.

The GUID generation framework in EMu will be programmatically customizable and extensible. However the aim for KE is to provide sufficient (non programming) configuration capabilities to allow most EMu institutions to generate their desired GUIDs without further consulting by KE. But inevitably some customers will desire variations to the functionality which will require (server-side) programming and KE will evaluate that case-by-case and quote for consulting work as needed.

Will the GUID generation functionality be configured on a module-by-module basis (in other words, we could turn it on for Catalogue only)?

Yes you will be able to set GUID generation just for the Catalogue. The GUID generation capabilities will be configurable module-by-module. Customers will be able to designate which modules should have automatic GUID generation and what GUID formats should be generated for records in that module. Auto generation will first check to see whether the record has a GUID in the desired format, and if not generate one. A few low level core EMu modules will be permanently excluded from GUID generation (Audit, Registry, possibly others).

Within a module, would it be possible to generate one format of GUID for some records, and another format for others?  I'm thinking of biological vs. archives records, etc.

Yes this will be possible but it will require local server-side program customization. Customization to switch GUID generation on/off based on values in key fields would be quite small scale. Whether KE would have to quote for such work would have to evaluated case-by-case. KE believes we will be able to provide some localization templates that illustrate how simple field value inclusion/exclusion can be wrapped around the GUID generation. Please note the EMu GUID infrastructure would allow these localizations to be retained through later upgrades to EMu (which is standard EMu policy).

Also, if GUID generation functionality was turned on for a module, would it still be possible for us to populate additional GUIDs via import?

Yes. The GUID setup uses regular EMu fields which can be populated via any EMu method. Access to the GUID fields is controlled in the standard way by the EMu registry.

Regards,

Ian

Ian Turnbull
Chief Operating Officer
KE Software

Edited by: Ian Turnbull (Axiell Melbourne) - 20-Sep-13 13:46:11

Ian Turnbull
Chief Operating Officer
KE Software.

Ian Turnbull (Axiell Melbourne)
useravatar
Offline
6 Posts
Website 
Administrator has disabled public posting. Please login or register in order to proceed.
There are 0 guests and 0 other users also viewing this topic

Board Info

Board Stats
 
Total Topics:
601
Total Polls:
0
Total Posts:
1362
User Info
 
Total Users:
822
Newest User:
Vijay Abhichandani (Axiell Ottawa)
Members Online:
0
Guests Online:
299

Online: 
There are no members online