# data[].attributes.headline
Accessibility on the staff side in terms of font size, color contrast, etc.  Obviously this should, and I trust will, happen for the public side but the staff side is often overlooked and it's a consideration for those who spend their entire day working in the system.  

# data[].attributes.subject
Accessibility on the staff side in terms of font size, color contrast, etc.  Obviously this should, and I trust will, happen for the public side but the staff side is often overlooked and it's a consideration for those who spend their entire day working in the system.  

# data[].attributes.headline
Yes, but not in the single-system approach. I like the idea of having cutting-edge approaches for certain "micro" services, and allowing more standards-based stability elsewhere.

# data[].attributes.subject
Yes, but not in the single-system approach. I like the idea of having cutting-edge approaches for certain "micro" services, and allowing more standards-based stability elsewhere.

# data[].attributes.headline
Allow for multiple workflows to accommodate different processes in SC compared to general collections

# data[].attributes.subject
Allow for multiple workflows to accommodate different processes in SC compared to general collections

# data[].attributes.headline
If customizable, involve staff in creating customization wish list and implementation

# data[].attributes.subject
If customizable, involve staff in creating customization wish list and implementation

# data[].attributes.body
Have the ability to host e-resources files, such as those that arrive at Yale in PDF and need to be ingested into FindIt.

# data[].attributes.headline
A clear sense of what's on and off the table for system functionality in the short, medium, and long term

# data[].attributes.subject
A clear sense of what's on and off the table for system functionality in the short, medium, and long term

# data[].attributes.headline
higher comfort level with change - more practice with change management.

# data[].attributes.subject
higher comfort level with change - more practice with change management.

# data[].attributes.headline
Define what support exisits for system as early as possible 

# data[].attributes.subject
Define what support exisits for system as early as possible 

# data[].attributes.body
cutting edge is great and we need to keep pace with new technologies,. however, this requires continuous change which can be disruptive. need at least a semblance of stability in our core acq and cataloging functions

# data[].attributes.headline
Ensure "special collections" at all levels has an active, robust, and continuing presence in all conversations of an new implementation

# data[].attributes.subject
Ensure "special collections" at all levels has an active, robust, and continuing presence in all conversations of an new implementation

# data[].attributes.body
To me this means being agile with rolling out improvements; developing the staff capacity and expertise to control and refine our critical systems; invest in improving shared systems to benefit the wider community rather than paying a vendor and having our contributions go to their profits rather than the greater good.

# data[].attributes.headline
Speed of retrieval after search needs to be considered.  Can the ILS handle a large volume of results and display them in a reasonable amount of time?

# data[].attributes.subject
Speed of retrieval after search needs to be considered.  Can the ILS handle a large volume of results and display them in a reasonable amount of time?

# data[].attributes.headline
Information about the experiences of other repositories with the system

# data[].attributes.subject
Information about the experiences of other repositories with the system

# data[].attributes.headline
Opportunities for data remediation and clean-up

# data[].attributes.subject
Opportunities for data remediation and clean-up

# data[].attributes.headline
better analytics on search terms used, number of times records have been viewed, etc.

# data[].attributes.subject
better analytics on search terms used, number of times records have been viewed, etc.

# data[].attributes.headline
Opportunities for more staff focus on bibliometrics

# data[].attributes.subject
Opportunities for more staff focus on bibliometrics

# data[].attributes.body
We need to build in a very generous time period between when the system is "up" and when we roll over from Voyager.

# data[].attributes.headline
Over the past few years, we've had a lot of exciting developments in archival discovery with the implementation of Archives at Yale, which really improved the patron experience.  It would be great to see the same thing happen on the OPAC side, with enhancements and improvements for staff and patrons.  It is also an opportunity for staff who perhaps have been more focused on ASpace recently to re-engage with our ILS.

# data[].attributes.subject
Over the past few years, we've had a lot of exciting developments in archival discovery with the implementation of Archives at Yale, which really improved the patron experience.  It would be great to see the same thing happen on the OPAC side, with enhancements and improvements for staff and patrons.  It is also an opportunity for staff who perhaps have been more focused on ASpace recently to re-engage with our ILS.

# data[].attributes.headline
Help from educators in designing training

# data[].attributes.subject
Help from educators in designing training

# data[].attributes.body
It's essential that special collections staff be involved in gathering and testing search scenarios

# data[].attributes.headline
Asynchronous training options with exercises (in addition to hands-on training)

# data[].attributes.subject
Asynchronous training options with exercises (in addition to hands-on training)

# data[].attributes.headline
Lots of short videos to watch to aid training

# data[].attributes.subject
Lots of short videos to watch to aid training

# data[].attributes.body
A clearly communicated timeline about how various aspects of the migration will play out, including clarity around our "red zone" issues and how those are being contended with in the migration

# data[].attributes.headline
Vendors available to come do the training, at least initially

# data[].attributes.subject
Vendors available to come do the training, at least initially

# data[].attributes.body
especially after experience with DBText to Voyager transition

# data[].attributes.headline
ACCU: depends on the person and the tool

# data[].attributes.subject
ACCU: depends on the person and the tool

# data[].attributes.headline
I think giving staff ample time to practice working in the new system. Having some boilerplate responses for patron questions.

# data[].attributes.subject
I think giving staff ample time to practice working in the new system. Having some boilerplate responses for patron questions.

# data[].attributes.headline
Bibliographic Description Unit: mostly comfortable (as far as catalogers go)

# data[].attributes.subject
Bibliographic Description Unit: mostly comfortable (as far as catalogers go)

# data[].attributes.headline
Likely lots of small things, like creating labels

# data[].attributes.subject
Likely lots of small things, like creating labels

# data[].attributes.body
e.g. scan a barcode to print a replacement label.

Would be great, I think, to have some of these services to be abstracted and available for whatever system of record.

# data[].attributes.headline
integrated workflow processes eg acquitisition approvals - pass on and alerts to next person who need to do 

# data[].attributes.subject
integrated workflow processes eg acquitisition approvals - pass on and alerts to next person who need to do 

# data[].attributes.headline
linking to other description in the system - eg bound withs

# data[].attributes.subject
linking to other description in the system - eg bound withs

# data[].attributes.headline
Embedded requesting of materials described in ArchivesSpace

# data[].attributes.subject
Embedded requesting of materials described in ArchivesSpace

# data[].attributes.headline
Integrate with an as-yet to be developed acquisitions workflow management system

# data[].attributes.subject
Integrate with an as-yet to be developed acquisitions workflow management system

# data[].attributes.body
Can't get into specifics, but would love to see APIs allow external systems to link to records, even if they are not public.

# data[].attributes.body
for DRMS, preferably through MetadataCloud (s.s.)

# data[].attributes.headline
Integration with Preservation's instance of TMS (preferably through Metadata Cloud)

# data[].attributes.subject
Integration with Preservation's instance of TMS (preferably through Metadata Cloud)

# data[].attributes.headline
I'm not sure, but I think the process for linking bound-withs may need to be rethought.

# data[].attributes.subject
I'm not sure, but I think the process for linking bound-withs may need to be rethought.

# data[].attributes.body
(s.s.)

# data[].attributes.body
I'm a little out of the loop on this, but when we set up the management of restrictions in Voyager using statistical categories, we were aware that there was no guarantee of forward migration given that those were system-speciflc to Voyager. We'll need to figure out how to migrate those as they are a crucial component to the Aeon integration.

# data[].attributes.headline
ASpace to Voyager integration for accession records

# data[].attributes.subject
ASpace to Voyager integration for accession records

# data[].attributes.headline
Adding DCS objects within catalog record

# data[].attributes.subject
Adding DCS objects within catalog record

# data[].attributes.body
Requirements gathered, scheduled for development. (s.s.)

# data[].attributes.headline
decoupled as much as possible to avoid breakdown of system when dependencies are unknown or overlooked

# data[].attributes.subject
decoupled as much as possible to avoid breakdown of system when dependencies are unknown or overlooked

# data[].attributes.headline
Being able to view the digitized image, or at least a thumbnail, as currently happens in ASpace

# data[].attributes.subject
Being able to view the digitized image, or at least a thumbnail, as currently happens in ASpace

# data[].attributes.body
OnBase has extensive API support, so ideally we would enjoy bi-directional links - documents added via OnBase being visible within the ILS and being able to add documents to OnBase within the ILS. In both cases creating/maintaining links between records (at least acquisition records) and related documents.

# data[].attributes.headline
Capture record histories rather than an unsatisfying "LOAD", so we can retain staff interactions with a record 

# data[].attributes.subject
Capture record histories rather than an unsatisfying "LOAD", so we can retain staff interactions with a record 

# data[].attributes.headline
Through best-of-breed tools (e.g. MarcEdit)

# data[].attributes.subject
Through best-of-breed tools (e.g. MarcEdit)

# data[].attributes.headline
Allowed patrons to share more easily to social media or to their own systems (easy bib, etc). 

# data[].attributes.subject
Allowed patrons to share more easily to social media or to their own systems (easy bib, etc). 

# data[].attributes.headline
With robust and sustained support from Library IT

# data[].attributes.subject
With robust and sustained support from Library IT

# data[].attributes.headline
Integration that would allow patrons to see their ILL/BD requests and special collections requests within one view or at least being able to "toggle" without having to log into different systems, for Yale and Non-Yale patrons.

# data[].attributes.subject
Integration that would allow patrons to see their ILL/BD requests and special collections requests within one view or at least being able to "toggle" without having to log into different systems, for Yale and Non-Yale patrons.

# data[].attributes.headline
Hyland OnBase (document management system)

# data[].attributes.subject
Hyland OnBase (document management system)

# data[].attributes.body
The university is rolling out OnBase as our new document management system. At minimum the library will use it for managing invoices, but likely will adopt it for collection mangement documetnation generally. Would be great to access those documents within the ILS.

# data[].attributes.headline
propose updates corrections from public interface for review, accept, or decline in staff user interface

# data[].attributes.subject
propose updates corrections from public interface for review, accept, or decline in staff user interface

# data[].attributes.headline
Robust and extensive statistical reporting

# data[].attributes.subject
Robust and extensive statistical reporting

# data[].attributes.headline
Hover-over information, such as showing what the location codes stand for

# data[].attributes.subject
Hover-over information, such as showing what the location codes stand for

# data[].attributes.headline
automated reuse of data for additional purposes - eg creat a wikipedia record; add to a libguide; 

# data[].attributes.subject
automated reuse of data for additional purposes - eg creat a wikipedia record; add to a libguide; 

# data[].attributes.headline
Forward migration of acquisitions records from Voyager

# data[].attributes.subject
Forward migration of acquisitions records from Voyager

# data[].attributes.headline
A way to limit to fully and partially digitized materials

# data[].attributes.subject
A way to limit to fully and partially digitized materials

# data[].attributes.headline
Integration with external authorities and vocabuliaries

# data[].attributes.subject
Integration with external authorities and vocabuliaries

# data[].attributes.headline
Item-specific information needs to be easily viewable

# data[].attributes.subject
Item-specific information needs to be easily viewable

# data[].attributes.headline
Robust tracking of material at all levels

# data[].attributes.subject
Robust tracking of material at all levels

# data[].attributes.body
Embedded IIIF viewer

# data[].attributes.headline
A "wikification" of records, to allow for versioning and seeing previous description and its change over time

# data[].attributes.subject
A "wikification" of records, to allow for versioning and seeing previous description and its change over time

# data[].attributes.headline
Integrated linking to OnBase (new campus document management system)

# data[].attributes.subject
Integrated linking to OnBase (new campus document management system)

# data[].attributes.body
Allow appropriate transparency about acquisitions while securing private information: prices paid? identity of anonymous donors?

# data[].attributes.headline
Currently there is a "history" for bib, mfhd, and item records that can be helpful when we are trying to find missing materials or have other information.  Ideally, this would be retained in the new system and perhaps the entries could be more specific than they currently are. 

# data[].attributes.subject
Currently there is a "history" for bib, mfhd, and item records that can be helpful when we are trying to find missing materials or have other information.  Ideally, this would be retained in the new system and perhaps the entries could be more specific than they currently are. 

# data[].attributes.headline
Advance access to a test/sandbox environment that would enable staff to start training and developing new workflows prior to a production switchover to the new system.

# data[].attributes.subject
Advance access to a test/sandbox environment that would enable staff to start training and developing new workflows prior to a production switchover to the new system.

# data[].attributes.headline
In user interface, it should not collapse different editions/printings/etc. into one single view.

# data[].attributes.subject
In user interface, it should not collapse different editions/printings/etc. into one single view.

# data[].attributes.headline
Allow for transfer/porting of metadata and information from ILS to and fronm other systems, such as ArchivesSpace, DAMS, etc

# data[].attributes.subject
Allow for transfer/porting of metadata and information from ILS to and fronm other systems, such as ArchivesSpace, DAMS, etc

# data[].attributes.headline
Provides data validations (e.g. at the record and relationship levels)

# data[].attributes.subject
Provides data validations (e.g. at the record and relationship levels)

# data[].attributes.headline
Permanent retention of acquisition records

# data[].attributes.subject
Permanent retention of acquisition records

# data[].attributes.headline
Better display and handling of "bound-withs", multi volume sets, analytics, serials, and records for printed items within archives (which don't have finding aids).  All can be tricky for patrons to request and necessitate staff time to troubleshoot requests

# data[].attributes.subject
Better display and handling of "bound-withs", multi volume sets, analytics, serials, and records for printed items within archives (which don't have finding aids).  All can be tricky for patrons to request and necessitate staff time to troubleshoot requests

# data[].attributes.body
Intuitive and up front advanced searching functionality

# data[].attributes.headline
Easy input of non-roman characters and diacritics

# data[].attributes.subject
Easy input of non-roman characters and diacritics

# data[].attributes.headline
Interoperability with external systems (e.g., Aeon as already noted)

# data[].attributes.subject
Interoperability with external systems (e.g., Aeon as already noted)

# data[].attributes.headline
integrate with our other systems; preservica, as , aeon

# data[].attributes.subject
integrate with our other systems; preservica, as , aeon