Please note: This post highlights our current thinking on this feature. Please help us improve it — share your questions, constructive feedback and ideas in the comments below.
We’ve gotten some user feedback on our Location CRUD (create, read, update and delete) design. Location CRUD is done in Settings > Organization > Location setup. This user feedback has resulted in some proposed modifications we’d like to get broader input on.
Summary of proposed changes:
Names and codes should only need to be unique within the context of their hierarchy
Story added: UIORG-95, With this change, you could reuse the location name “Reference” in different libraries or have a “Main library” on two different campuses, for example.
- Configuration of Location display format. Since location names and codes won’t always be unique, FOLIO needs to support the inclusion of hierarchy elements (e.g. Institution, Campus and Library) in the location display so that the necessary context is apparent. To this end, we have designed a feature that allows tenant configuration of location display. See the “FOLIO location display name configuration” on this mockup
- Auto-generation of Location hierarchy codes (based on manually entered location component codes) is essential to the usability of this feature. See “Location hierarchy code configuration” field on this mockup
Details on auto-generation of location hierarchy codes:
A. When configuring location hierarchy codes, where do the component codes (e.g. for Campus and Library) come from? Are they auto-generated based on the first 3 letters of the name?
— The component codes are not auto-generated. They are manually added as part of the Institution, Campus and Library CRUD. See this screenshot for how this is done. These codes can be whatever you want; two letters, three letters, capitals, lowercase, numbers…
B. Where does the location hierarchy code display?
— On the location record in Settings (read-only display) (see mockup)
— In the location selection menu on the holding and item records
— Anywhere that location displays (e.g. Loans, Check in, Requests) IF you make Location hierarchy code part of the FOLIO location display name (see item #2 above)
C. Are component codes required when creating location hierarchy components?
— They are not currently, but we would make them required when implementing this change
D. Do the component codes need to be unique?
— Yes, just like component names, they need to be unique within their own hierarchy
E. When creating a location hierarchy code format, what flexibility do I have?
— I can include the component codes in whatever order I want them and I can use whatever separators I want (dashes, slashes etc) but I must include all elements of the hierarchy
What do you think of these changes? Any questions or concerns? Let us know in the comments.