Re: [CODE4LIB] Back-of-house software

[Cary Gordon]

There was someone in the Drupal in Libraries BoF today at DrupalCon who 
mentioned it. But who?

Cary

> On May 11, 2016, at 10:12 AM, Charlie Morris  wrote:
> 
> I wonder if anyone out there is using RedHen (
> https://www.drupal.org/project/redhen). I've always been curious about it.
> 
> On Wed, May 11, 2016 at 11:01 AM, Mike Smorul  wrote:
> 
>> I'll put up a vote for redmine. We use it w/ a few commercial plugins from
>> redminecrm (helpdesk, crm, and ticket-checklists) to handle most of our
>> internal procedures and process documentation. Specifically its positioned
>> to handle the following:
>> 
>> * Internal infrastructure changelogs (tickets) and documentation (wiki)
>> * Helpdesk response
>> * Order tracking.
>> * Internal/organization wiki.
>> * Individual project progress, documentation and issue tracking.
>> 
>> One feature we make heavy use of is nesting projects to allows us to both
>> segment work and still see an overview of what's going on w/in a
>> department.
>> 
>> There are a few things we don't use it for:
>> * code browsing - handled by github or an internal gitlab server
>> * office document storage - handled internally via file-share or sharepoint
>> * public project websites - either main drupal or ghpages
>> 
>> On Wed, May 11, 2016 at 9:46 AM, Erin White  wrote:
>> 
>>> Following this thread closely to see what y'all use.
>>> 
>>> We evaluated our institution's IT support desk software and found the
>>> interface pretty hostile to problem-submitters. Instead we've stuck with
>>> our own in-house problem reporting system that has a much simpler user
>>> interface. It meets many business needs but doesn't integrate with our
>>> other systems (documentation, etc.) and our software development
>> workflow.
>>> So we have some things we could be doing much better.
>>> 
>>> --
>>> Erin White
>>> Web Systems Librarian, VCU Libraries
>>> (804) 827-3552 | erwh...@vcu.edu | www.library.vcu.edu
>>> 
>>> On Wed, May 11, 2016 at 3:48 AM, Ben Companjen <
>> ben.compan...@dans.knaw.nl
 
>>> wrote:
>>> 
 Hi Stuart,
 
 First thought (or what should have been my first thought): what
>>> problem(s)
 are you trying to solve?
 I sometime wish I had software that is better geared for service
 management (including incident management, CRM and documentation), but
>> in
 our small organisation with three main services it has already been
>>> helpful
 to structure the information differently and get it together in
>>> well-known
 places. For the Dataverse service that I'm managing we use Google
 Drive/Docs, ownCloud and JIRA.
 
 Incident and service request management is the most important
 process/business function that I think would benefit from software
>>> support.
 Emails, tasks and notes in various places aren't enough anymore to keep
 track of problems and questions. JIRA helps a little, but not all
>>> requests
 relate to software problems and I don't want to use it for every
 simple-to-answer question.
 
 Have you asked your institution's IT service desk for suggestions? They
 might be able to support when you choose the same software. Our IT uses
>>> RT
 and seems happy with it. I'm hoping to get a queue for
>> Dataverse-related
 requests in their system.
 
 Hope this helps.
 
 Ben
 
 
 
 
 On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" <
 CODE4LIB@LISTSERV.ND.EDU on behalf of syea...@gmail.com> wrote:
 
> I’m looking for recommendations for software to run our much of our
> academic library back-of-house business-as-usual work. Things like
 incident
> management, CRM, documentation management, etc across three tiers of
> support.
> 
> We’re looking for something more structured than a mediawiki wiki
>> (which
> we’ve got) and probably less structured than full-blown ITIL. We’re
>>> happy
> with open source or proprietary,  self-hosted or cloud solution, but
>>> we’re
> not happy to pay the kinds of money that Alemba (formerly VMWare) are
> asking for vFire Core (formerly VMware Service Manager).
> 
> We have library management system (ALMA), a discovery system (PRIMO),
>> a
> website (httpd, drupal), a proxy (EZproxy) and a copyright management
> system (Talis Aspire). Our institution provides us with user
>> management,
> physical access management, VM host, email and physical
>> infrastructure.
> 
> Thoughts?
> 
> --
> ...let us be heard from red core to black sky
 
>>> 
>> 

[CODE4LIB] Where can I find a basic set of user stories for a digital library?

[Wilhelmina Randtke]

Does anyone have a set of user stories for a digital library that you'd be
willing to share?  Or, is there a good place to look this up and pull a set?

I'm working with these types of materials:  old photos, digitized books,
digitized newspapers, ETDs.  Pretty much the basics of digital library
content.  I'm interested in a listing of ways people would use these, so I
can better understand what the platforms I'm working with do well and where
gaps are.

-Wilhelmina Randtke

[CODE4LIB] NASIG 2016 Conference – MAY 18 EARLY BIRD REGISTRATION DEADLINE

[public...@nasig.org]

[CODE4LIB] Job Posting: Technology Librarian - Loyola / Notre Dame Library, Baltimore, MD

[Katy O'Neill]

The Loyola / Notre Dame Library has an exciting opportunity leading digital and 
technology services!

Technology Librarian
The Loyola ▪ Notre Dame Library seeks a dynamic, 
innovative, and experienced individual to provide leadership to support digital 
and technology services.  The Technology Librarian will support day-to-day 
operations with some supervisory responsibility, and provide strategic 
direction for digital and technology services that enable research, teaching, 
and learning programs in the Library.

The successful candidate will communicate effectively and work collaboratively 
with units throughout the Library to support a range of services that may 
include discovery, digital library initiatives, and instruction.  The position 
will coordinate services with technical staff at University System of Maryland 
and Affiliated Institutions (USMAI) and also work 
collaboratively with information technology departments at Loyola University 
Maryland and Notre Dame of Maryland 
University.  A demonstrated ability to thrive in a 
changing work environment and a commitment to professional development are 
important. The candidate will understand and be able to communicate 
library-related technology trends that support user-centered library services 
to a diverse population of undergraduates, graduate students, and faculty.

Position Responsibilities:

  *   Provide strategic vision and leadership of Library technology operations 
and initiatives to support faculty and students.
  *Lead day-to-day technical operations working closely with USMAI’s 
Consortial Library Applications Support (CLAS) team including:
 *   Integrating, troubleshooting, and resolving various issues with 
purchased and licensed software;
 *   Resolving authentication problems and ensuring smooth and reliable 
access; and
 *   Working with vendor-based APIs and web services.

  *   Lead Technology Services department staff and student assistants.
  *   Work closely with the information technology departments of both Loyola 
and Notre Dame and outside partners to develop and maintain technological 
infrastructure and support future technology initiatives and digital services.
  *   Collect and use data to inform decisions on technology integration.
  *Lead planning for the Library’s website and mobile application 
initiatives.
  *Provide input to the Library Administration on budgeting, reporting and 
compliance as related to technology services.
  *   Engage and remain current on information technology and digital library 
trends.

Required Qualifications:

  *   ALA-accredited Master’s in Library/Information Science or equivalent;
  *2+ years professional experience in evaluating, developing, and 
maintaining information applications;
  *   Familiarity with library systems and applications such as OpenURL (link 
resolvers), proxy servers, and standards such as Z39.50;
  *   Working knowledge in current web programming languages and technologies 
such as PHP or JavaScript and SQL;
  *   Working knowledge of web development, design, frameworks, and standards, 
including HTML and CSS;
  *   Ability to utilize and design APIs and web services;
  *   Demonstrated analytical and project management skills;
  *   Demonstrated effective oral, written, and interpersonal communication 
skills;
  *   Ability to work creatively both individually and collaboratively in a 
team-based environment.

Preferred Qualifications:

  *   Experience in higher education;
  *   Familiarity with authentication and web security protocols such as 
Shibboleth, LDAP, and SSL;
  *   Familiarity with institutional repositories;
  *   Knowledge of multiple formats for representing data such as XML or JSON;
  *   Experience working with open source software;
  *   Familiarity with a major programming language such as Python, Ruby, or 
Java.

About the Library:

The Loyola   Notre Dame Library, located in a residential 
area of northern Baltimore City, is a recently admitted member of University 
System of Maryland and Affiliated Institutions (USMAI) 
and serves two universities: Loyola University Maryland and Notre Dame of 
Maryland University.  Loyola University Maryland, a 
member of the Association of Jesuit Colleges and Universities, is recognized 
for excellence in teaching and learning while Notre Dame of Maryland 
University is a leader in the education of women and 
non-traditional students.  The Library serves a total population of 7,448 FTE 
that includes 5,540 FTE at Loyola and 1,908 FTE at Notre Dame.

The Library offers an excellent benefits package that includes medical, access 
to dental, life, and disability insurance, as well as TIAA retirement. 
Successful candidates will be subject to a pre‐employment background check.

The Loyola ▪ Notre Dame Library is an equal opportunity employer and does not 
discriminate on the basis of race, color, national and ethnic origin, religion, 
sex, sexual orientation, disability, 

Re: [CODE4LIB] Back-of-house software

[Charlie Morris]

I wonder if anyone out there is using RedHen (
https://www.drupal.org/project/redhen). I've always been curious about it.

On Wed, May 11, 2016 at 11:01 AM, Mike Smorul  wrote:

> I'll put up a vote for redmine. We use it w/ a few commercial plugins from
> redminecrm (helpdesk, crm, and ticket-checklists) to handle most of our
> internal procedures and process documentation. Specifically its positioned
> to handle the following:
>
> * Internal infrastructure changelogs (tickets) and documentation (wiki)
> * Helpdesk response
> * Order tracking.
> * Internal/organization wiki.
> * Individual project progress, documentation and issue tracking.
>
> One feature we make heavy use of is nesting projects to allows us to both
> segment work and still see an overview of what's going on w/in a
> department.
>
> There are a few things we don't use it for:
> * code browsing - handled by github or an internal gitlab server
> * office document storage - handled internally via file-share or sharepoint
> * public project websites - either main drupal or ghpages
>
> On Wed, May 11, 2016 at 9:46 AM, Erin White  wrote:
>
> > Following this thread closely to see what y'all use.
> >
> > We evaluated our institution's IT support desk software and found the
> > interface pretty hostile to problem-submitters. Instead we've stuck with
> > our own in-house problem reporting system that has a much simpler user
> > interface. It meets many business needs but doesn't integrate with our
> > other systems (documentation, etc.) and our software development
> workflow.
> > So we have some things we could be doing much better.
> >
> > --
> > Erin White
> > Web Systems Librarian, VCU Libraries
> > (804) 827-3552 | erwh...@vcu.edu | www.library.vcu.edu
> >
> > On Wed, May 11, 2016 at 3:48 AM, Ben Companjen <
> ben.compan...@dans.knaw.nl
> > >
> > wrote:
> >
> > > Hi Stuart,
> > >
> > > First thought (or what should have been my first thought): what
> > problem(s)
> > > are you trying to solve?
> > > I sometime wish I had software that is better geared for service
> > > management (including incident management, CRM and documentation), but
> in
> > > our small organisation with three main services it has already been
> > helpful
> > > to structure the information differently and get it together in
> > well-known
> > > places. For the Dataverse service that I'm managing we use Google
> > > Drive/Docs, ownCloud and JIRA.
> > >
> > > Incident and service request management is the most important
> > > process/business function that I think would benefit from software
> > support.
> > > Emails, tasks and notes in various places aren't enough anymore to keep
> > > track of problems and questions. JIRA helps a little, but not all
> > requests
> > > relate to software problems and I don't want to use it for every
> > > simple-to-answer question.
> > >
> > > Have you asked your institution's IT service desk for suggestions? They
> > > might be able to support when you choose the same software. Our IT uses
> > RT
> > > and seems happy with it. I'm hoping to get a queue for
> Dataverse-related
> > > requests in their system.
> > >
> > > Hope this helps.
> > >
> > > Ben
> > >
> > >
> > >
> > >
> > > On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" <
> > > CODE4LIB@LISTSERV.ND.EDU on behalf of syea...@gmail.com> wrote:
> > >
> > > >I’m looking for recommendations for software to run our much of our
> > > >academic library back-of-house business-as-usual work. Things like
> > > incident
> > > >management, CRM, documentation management, etc across three tiers of
> > > >support.
> > > >
> > > >We’re looking for something more structured than a mediawiki wiki
> (which
> > > >we’ve got) and probably less structured than full-blown ITIL. We’re
> > happy
> > > >with open source or proprietary,  self-hosted or cloud solution, but
> > we’re
> > > >not happy to pay the kinds of money that Alemba (formerly VMWare) are
> > > >asking for vFire Core (formerly VMware Service Manager).
> > > >
> > > >We have library management system (ALMA), a discovery system (PRIMO),
> a
> > > >website (httpd, drupal), a proxy (EZproxy) and a copyright management
> > > >system (Talis Aspire). Our institution provides us with user
> management,
> > > >physical access management, VM host, email and physical
> infrastructure.
> > > >
> > > >Thoughts?
> > > >
> > > >--
> > > >...let us be heard from red core to black sky
> > >
> >
>

Re: [CODE4LIB] Back-of-house software

[Shaughnessy, Peggy]

+1 for Redmine.

Peggy Shaughnessy
Web Applications Developer
Poudre River Public Library District
301 E. Olive Street
Fort Collins, Colorado 80524
970.221.6716
pshaughne...@poudrelibraries.org
http://poudrelibraries.org

From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Mike Smorul 
[msmo...@gmail.com]
Sent: Wednesday, May 11, 2016 9:01 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Back-of-house software

I'll put up a vote for redmine. We use it w/ a few commercial plugins from
redminecrm (helpdesk, crm, and ticket-checklists) to handle most of our
internal procedures and process documentation. Specifically its positioned
to handle the following:

* Internal infrastructure changelogs (tickets) and documentation (wiki)
* Helpdesk response
* Order tracking.
* Internal/organization wiki.
* Individual project progress, documentation and issue tracking.

One feature we make heavy use of is nesting projects to allows us to both
segment work and still see an overview of what's going on w/in a department.

There are a few things we don't use it for:
* code browsing - handled by github or an internal gitlab server
* office document storage - handled internally via file-share or sharepoint
* public project websites - either main drupal or ghpages

On Wed, May 11, 2016 at 9:46 AM, Erin White  wrote:

> Following this thread closely to see what y'all use.
>
> We evaluated our institution's IT support desk software and found the
> interface pretty hostile to problem-submitters. Instead we've stuck with
> our own in-house problem reporting system that has a much simpler user
> interface. It meets many business needs but doesn't integrate with our
> other systems (documentation, etc.) and our software development workflow.
> So we have some things we could be doing much better.
>
> --
> Erin White
> Web Systems Librarian, VCU Libraries
> (804) 827-3552 | erwh...@vcu.edu | www.library.vcu.edu
>
> On Wed, May 11, 2016 at 3:48 AM, Ben Companjen  >
> wrote:
>
> > Hi Stuart,
> >
> > First thought (or what should have been my first thought): what
> problem(s)
> > are you trying to solve?
> > I sometime wish I had software that is better geared for service
> > management (including incident management, CRM and documentation), but in
> > our small organisation with three main services it has already been
> helpful
> > to structure the information differently and get it together in
> well-known
> > places. For the Dataverse service that I'm managing we use Google
> > Drive/Docs, ownCloud and JIRA.
> >
> > Incident and service request management is the most important
> > process/business function that I think would benefit from software
> support.
> > Emails, tasks and notes in various places aren't enough anymore to keep
> > track of problems and questions. JIRA helps a little, but not all
> requests
> > relate to software problems and I don't want to use it for every
> > simple-to-answer question.
> >
> > Have you asked your institution's IT service desk for suggestions? They
> > might be able to support when you choose the same software. Our IT uses
> RT
> > and seems happy with it. I'm hoping to get a queue for Dataverse-related
> > requests in their system.
> >
> > Hope this helps.
> >
> > Ben
> >
> >
> >
> >
> > On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" <
> > CODE4LIB@LISTSERV.ND.EDU on behalf of syea...@gmail.com> wrote:
> >
> > >I’m looking for recommendations for software to run our much of our
> > >academic library back-of-house business-as-usual work. Things like
> > incident
> > >management, CRM, documentation management, etc across three tiers of
> > >support.
> > >
> > >We’re looking for something more structured than a mediawiki wiki (which
> > >we’ve got) and probably less structured than full-blown ITIL. We’re
> happy
> > >with open source or proprietary,  self-hosted or cloud solution, but
> we’re
> > >not happy to pay the kinds of money that Alemba (formerly VMWare) are
> > >asking for vFire Core (formerly VMware Service Manager).
> > >
> > >We have library management system (ALMA), a discovery system (PRIMO), a
> > >website (httpd, drupal), a proxy (EZproxy) and a copyright management
> > >system (Talis Aspire). Our institution provides us with user management,
> > >physical access management, VM host, email and physical infrastructure.
> > >
> > >Thoughts?
> > >
> > >--
> > >...let us be heard from red core to black sky
> >
>

Re: [CODE4LIB] Back-of-house software

[Mike Smorul]

I'll put up a vote for redmine. We use it w/ a few commercial plugins from
redminecrm (helpdesk, crm, and ticket-checklists) to handle most of our
internal procedures and process documentation. Specifically its positioned
to handle the following:

* Internal infrastructure changelogs (tickets) and documentation (wiki)
* Helpdesk response
* Order tracking.
* Internal/organization wiki.
* Individual project progress, documentation and issue tracking.

One feature we make heavy use of is nesting projects to allows us to both
segment work and still see an overview of what's going on w/in a department.

There are a few things we don't use it for:
* code browsing - handled by github or an internal gitlab server
* office document storage - handled internally via file-share or sharepoint
* public project websites - either main drupal or ghpages

On Wed, May 11, 2016 at 9:46 AM, Erin White  wrote:

> Following this thread closely to see what y'all use.
>
> We evaluated our institution's IT support desk software and found the
> interface pretty hostile to problem-submitters. Instead we've stuck with
> our own in-house problem reporting system that has a much simpler user
> interface. It meets many business needs but doesn't integrate with our
> other systems (documentation, etc.) and our software development workflow.
> So we have some things we could be doing much better.
>
> --
> Erin White
> Web Systems Librarian, VCU Libraries
> (804) 827-3552 | erwh...@vcu.edu | www.library.vcu.edu
>
> On Wed, May 11, 2016 at 3:48 AM, Ben Companjen  >
> wrote:
>
> > Hi Stuart,
> >
> > First thought (or what should have been my first thought): what
> problem(s)
> > are you trying to solve?
> > I sometime wish I had software that is better geared for service
> > management (including incident management, CRM and documentation), but in
> > our small organisation with three main services it has already been
> helpful
> > to structure the information differently and get it together in
> well-known
> > places. For the Dataverse service that I'm managing we use Google
> > Drive/Docs, ownCloud and JIRA.
> >
> > Incident and service request management is the most important
> > process/business function that I think would benefit from software
> support.
> > Emails, tasks and notes in various places aren't enough anymore to keep
> > track of problems and questions. JIRA helps a little, but not all
> requests
> > relate to software problems and I don't want to use it for every
> > simple-to-answer question.
> >
> > Have you asked your institution's IT service desk for suggestions? They
> > might be able to support when you choose the same software. Our IT uses
> RT
> > and seems happy with it. I'm hoping to get a queue for Dataverse-related
> > requests in their system.
> >
> > Hope this helps.
> >
> > Ben
> >
> >
> >
> >
> > On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" <
> > CODE4LIB@LISTSERV.ND.EDU on behalf of syea...@gmail.com> wrote:
> >
> > >I’m looking for recommendations for software to run our much of our
> > >academic library back-of-house business-as-usual work. Things like
> > incident
> > >management, CRM, documentation management, etc across three tiers of
> > >support.
> > >
> > >We’re looking for something more structured than a mediawiki wiki (which
> > >we’ve got) and probably less structured than full-blown ITIL. We’re
> happy
> > >with open source or proprietary,  self-hosted or cloud solution, but
> we’re
> > >not happy to pay the kinds of money that Alemba (formerly VMWare) are
> > >asking for vFire Core (formerly VMware Service Manager).
> > >
> > >We have library management system (ALMA), a discovery system (PRIMO), a
> > >website (httpd, drupal), a proxy (EZproxy) and a copyright management
> > >system (Talis Aspire). Our institution provides us with user management,
> > >physical access management, VM host, email and physical infrastructure.
> > >
> > >Thoughts?
> > >
> > >--
> > >...let us be heard from red core to black sky
> >
>

[CODE4LIB] Join the discussion @ ALA Annual: ‘Diverse and inclusive metadata: Developing cultural competencies in descriptive practices’

[Liz Woolcott]

***Apologies in advance for cross-posting***

The ALCTS Metadata Interest Group (MIG) will be hosting two programs on
“Diverse and inclusive metadata: Developing cultural competencies in
descriptive practices” during the 2016 ALA Annual Meeting in Orlando,
Florida in June.

This event will include two sessions on diversity in metadata-related
topics, one to take place on Saturday, June 25th from 10:30 to 11:30 and
another to take place during the regular business meeting of the ALCTS
Metadata Interest Group, on Sunday, June 26th at 8:30 am.

More information about each presentation, including the presenter and
specific presentation topics, can be found below or at the ALCTS Metadata
Interest Group blog

.

Additional events and programming related to diversity has been compiled by
the ALA Committee on Diversity (COD), along with the Office for Diversity,
Literacy and Outreach Services (ODLOS) and is available here:
https://sites.google.com/site/diversityrelatedevents/


*

Program Details:


*Saturday, June 25, 10:30am*

ALCTS sponsored program

Orange County Convention Center, Room W222

View on the ALA 2016 scheduler:
https://www.eventscribe.com/2016/ala-annual/fsPopup.asp?Mode=presInfo=139579



*1. Presentation Title*:  Impacts and Limitations of Culturally Responsive
Subject Headings in Tribal College Libraries

*Presenter*: Hannah Buckland, Leech Lake Tribal College

*Abstract*:

At tribal college libraries, prejudice embedded in controlled subject
vocabularies impedes students’ access to library materials.  The
Eurocentric terminology and viewpoint underpinning Library of Congress
Subject Headings, for example, often exclude tribes which have not been
federally recognized, favor anglicized generalization over local precision,
and treat concepts as mutually exclusive entities rather than overlapping,
interrelated pieces, as is more consistent with Native worldview.  Culture
directly molds classification; while no classification system is free of
cultural bias, mass-adopted classification systems like LCSH are troubling
in that they fail to reflect the full spectrum of diversity, both of the
collection and of library users.

At the Bezhigoogahbow Library—a joint-use academic/community library
serving both students of Leech Lake Tribal College LLTC and residents of
the Leech Lake Reservation in northern Minnesota—locally assigned,
culturally responsive subject headings improve access to LLTC-owned
materials.  Strategies for developing this metadata will be discussed.
Despite  local successes, however, library staff have observed students
familiar with the specialized vocabulary of the Bezhigoogahbow Library’s
online catalog struggle when conducting subject searches in the consortial
catalog and databases where LCSH remain the norm.  While inclusive metadata
may originate on a local level, implementation on a larger scale remains
necessary.


2. *PresentationTitle*: Hidden Stories, Inclusive Perspectives: Describing
Photographs of Jewish Refugees in Shanghai

*Presenter*: Rachel Wen-Paloutzian, Loyola Marymount University

*Abstract*:

When a collection of over 600 photographs and negatives was discovered in
the backlog of Loyola Marymount University LMU Library’s Department of
Archives and Special Collections, there were moments of surprise, intrigue,
and fascination. While information about the collection is limited, the
pictures have presumably been taken by Werner von Bolternstern, a
photographer and avid postcard collector, who donated the collection among
many others to LMU. The Werner von Bolternstern Shanghai Photograph and
negative Collection offers rare visual records and remarkable documentation
of life in Shanghai, China, from 1937 to 1949. Besides Shanghai urban
landscapes, historical  architecture, and street scenes, the photographs
offer a unique glimpse into the community of Jewish refugees living in
Shanghai at the time, including social life, businesses,  community events,
and government documents of Jewish refugees who fled the Holocaust.

Through contemplating various strategies for developing accurate and
inclusive metadata, this presentation will discuss the research and
creation process of descriptive metadata for the Werner von Bolternstern
Shanghai Photograph and Negative Collection. It will highlight ethical and
political questions in terms of how to appropriately describe the
photographs and how to create sensible description out of uncertainty. As
the presentation will evaluate controlled vocabularies and subject
headings, especially for images of people who might or might not be Jewish
refugees, it illustrates the importance  of metadata in historical
identification and narratives. Part of the research for metadata creation
is to understand the historical 

Re: [CODE4LIB] Back-of-house software

[Erin White]

Following this thread closely to see what y'all use.

We evaluated our institution's IT support desk software and found the
interface pretty hostile to problem-submitters. Instead we've stuck with
our own in-house problem reporting system that has a much simpler user
interface. It meets many business needs but doesn't integrate with our
other systems (documentation, etc.) and our software development workflow.
So we have some things we could be doing much better.

--
Erin White
Web Systems Librarian, VCU Libraries
(804) 827-3552 | erwh...@vcu.edu | www.library.vcu.edu

On Wed, May 11, 2016 at 3:48 AM, Ben Companjen 
wrote:

> Hi Stuart,
>
> First thought (or what should have been my first thought): what problem(s)
> are you trying to solve?
> I sometime wish I had software that is better geared for service
> management (including incident management, CRM and documentation), but in
> our small organisation with three main services it has already been helpful
> to structure the information differently and get it together in well-known
> places. For the Dataverse service that I'm managing we use Google
> Drive/Docs, ownCloud and JIRA.
>
> Incident and service request management is the most important
> process/business function that I think would benefit from software support.
> Emails, tasks and notes in various places aren't enough anymore to keep
> track of problems and questions. JIRA helps a little, but not all requests
> relate to software problems and I don't want to use it for every
> simple-to-answer question.
>
> Have you asked your institution's IT service desk for suggestions? They
> might be able to support when you choose the same software. Our IT uses RT
> and seems happy with it. I'm hoping to get a queue for Dataverse-related
> requests in their system.
>
> Hope this helps.
>
> Ben
>
>
>
>
> On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" <
> CODE4LIB@LISTSERV.ND.EDU on behalf of syea...@gmail.com> wrote:
>
> >I’m looking for recommendations for software to run our much of our
> >academic library back-of-house business-as-usual work. Things like
> incident
> >management, CRM, documentation management, etc across three tiers of
> >support.
> >
> >We’re looking for something more structured than a mediawiki wiki (which
> >we’ve got) and probably less structured than full-blown ITIL. We’re happy
> >with open source or proprietary,  self-hosted or cloud solution, but we’re
> >not happy to pay the kinds of money that Alemba (formerly VMWare) are
> >asking for vFire Core (formerly VMware Service Manager).
> >
> >We have library management system (ALMA), a discovery system (PRIMO), a
> >website (httpd, drupal), a proxy (EZproxy) and a copyright management
> >system (Talis Aspire). Our institution provides us with user management,
> >physical access management, VM host, email and physical infrastructure.
> >
> >Thoughts?
> >
> >--
> >...let us be heard from red core to black sky
>

Re: [CODE4LIB] Back-of-house software

[Ben Companjen]

Hi Stuart,

First thought (or what should have been my first thought): what problem(s) are 
you trying to solve?
I sometime wish I had software that is better geared for service management 
(including incident management, CRM and documentation), but in our small 
organisation with three main services it has already been helpful to structure 
the information differently and get it together in well-known places. For the 
Dataverse service that I'm managing we use Google Drive/Docs, ownCloud and JIRA.

Incident and service request management is the most important process/business 
function that I think would benefit from software support. Emails, tasks and 
notes in various places aren't enough anymore to keep track of problems and 
questions. JIRA helps a little, but not all requests relate to software 
problems and I don't want to use it for every simple-to-answer question.

Have you asked your institution's IT service desk for suggestions? They might 
be able to support when you choose the same software. Our IT uses RT and seems 
happy with it. I'm hoping to get a queue for Dataverse-related requests in 
their system.

Hope this helps.

Ben




On 10-05-16 23:42, "Code for Libraries on behalf of Stuart A. Yeates" 
 wrote:

>I’m looking for recommendations for software to run our much of our
>academic library back-of-house business-as-usual work. Things like incident
>management, CRM, documentation management, etc across three tiers of
>support.
>
>We’re looking for something more structured than a mediawiki wiki (which
>we’ve got) and probably less structured than full-blown ITIL. We’re happy
>with open source or proprietary,  self-hosted or cloud solution, but we’re
>not happy to pay the kinds of money that Alemba (formerly VMWare) are
>asking for vFire Core (formerly VMware Service Manager).
>
>We have library management system (ALMA), a discovery system (PRIMO), a
>website (httpd, drupal), a proxy (EZproxy) and a copyright management
>system (Talis Aspire). Our institution provides us with user management,
>physical access management, VM host, email and physical infrastructure.
>
>Thoughts?
>
>--
>...let us be heard from red core to black sky