Re: [CODE4LIB] Formalizing Code4Lib?

[Tom Johnson]

> Does anyone else want to self-nominate, to join a group to investigate
> making Code4Lib fiscally sustainable? Does someone want to *organize* that
> group? (Put the group on some communications medium, make deadlines, keep
> people on task -- stuff like that.) To be clear: nobody is proposing that
> it be a decision-making body; it would just be a fact-finding group, who
> would write up a list of the options to present to the larger community
> (and maybe preside over some kind of vote? I don't know, I guess the group
> will decide how to get the community to make decisions, too).

I would like to be a member of this group. Let's do the legal due
diligence, put out
feelers for partner orgs, and agree on a voting procedure.

- Tom

On Mon, Jun 13, 2016 at 2:46 PM, Coral Sheldon-Hess 
wrote:

> If we wait to start talking about it until conference 2017, that means
> conference committee 2018 will have to find its own temporary fiscal agent.
> Or 2018 could just not happen at all, I guess.
>
> Even if we do all the pre-work and just wait to make the decision at the
> conference, that doesn't leave much wiggle room for 2018.
>
> Also, if we only talk about it in person, we leave out everyone who is
> unable to attend conference. That's potentially a lot of interested people.
> I'm not sure we want to become *that *kind of library organization; our
> virtual decision-making model is one of our most attractive features, in my
> opinion (speaking as someone with disabilities and an uneven budget over
> the last few years).
>
> So I would encourage anyone interested in exploring fiscal
> sponsorship/becoming a nonprofit/[other solutions?] to form a group/task
> force/committee/whatever and to start researching options now, with a
> reasonable deadline for communicating back out to the whole community, so
> that we can all take part in making an informed decision before the 2018
> conference committee needs to get started (if, indeed, our community's
> consensus is to do 2018).
>
> Chad volunteered to help, and his knowledge about the 2016 process and
> budgets will make him incredibly helpful. We should take him up on that. I
> volunteered to help, and my previous research on starting a nonprofit
> and/or finding a fiscal sponsor for a previous project will make me also
> potentially helpful. Maybe we should take me up on that, or maybe the
> committee should not have anyone *quite* as in favor of radical change (or
> as new to the community) as I am. I defer to the group on that, once it
> forms.
>
> Does anyone else want to self-nominate, to join a group to investigate
> making Code4Lib fiscally sustainable? Does someone want to *organize* that
> group? (Put the group on some communications medium, make deadlines, keep
> people on task -- stuff like that.) To be clear: nobody is proposing that
> it be a decision-making body; it would just be a fact-finding group, who
> would write up a list of the options to present to the larger community
> (and maybe preside over some kind of vote? I don't know, I guess the group
> will decide how to get the community to make decisions, too).
>
> - Coral
>

Re: [CODE4LIB] Formalizing Code4Lib?

[Coral Sheldon-Hess]

If we wait to start talking about it until conference 2017, that means
conference committee 2018 will have to find its own temporary fiscal agent.
Or 2018 could just not happen at all, I guess.

Even if we do all the pre-work and just wait to make the decision at the
conference, that doesn't leave much wiggle room for 2018.

Also, if we only talk about it in person, we leave out everyone who is
unable to attend conference. That's potentially a lot of interested people.
I'm not sure we want to become *that *kind of library organization; our
virtual decision-making model is one of our most attractive features, in my
opinion (speaking as someone with disabilities and an uneven budget over
the last few years).

So I would encourage anyone interested in exploring fiscal
sponsorship/becoming a nonprofit/[other solutions?] to form a group/task
force/committee/whatever and to start researching options now, with a
reasonable deadline for communicating back out to the whole community, so
that we can all take part in making an informed decision before the 2018
conference committee needs to get started (if, indeed, our community's
consensus is to do 2018).

Chad volunteered to help, and his knowledge about the 2016 process and
budgets will make him incredibly helpful. We should take him up on that. I
volunteered to help, and my previous research on starting a nonprofit
and/or finding a fiscal sponsor for a previous project will make me also
potentially helpful. Maybe we should take me up on that, or maybe the
committee should not have anyone *quite* as in favor of radical change (or
as new to the community) as I am. I defer to the group on that, once it
forms.

Does anyone else want to self-nominate, to join a group to investigate
making Code4Lib fiscally sustainable? Does someone want to *organize* that
group? (Put the group on some communications medium, make deadlines, keep
people on task -- stuff like that.) To be clear: nobody is proposing that
it be a decision-making body; it would just be a fact-finding group, who
would write up a list of the options to present to the larger community
(and maybe preside over some kind of vote? I don't know, I guess the group
will decide how to get the community to make decisions, too).

- Coral

Re: [CODE4LIB] Formalizing Code4Lib?

[Salazar, Christina]

Am I misunderstanding Roy and/or Francis's intention though that given 
essentially a full year to plan C4L 2017, that either they or entities that 
they have strong connections too are willing to be the fiscal agent for 2017? 
That's what I thought they were implying. Both indicated that they could pull 
of a big conference for 2017.

So perhaps we can discuss the matter of finding a "permanent" fiscal agent face 
to face at conference in 2017

Christina Salazar
Systems Librarian
John Spoor Broome Library
California State University, Channel Islands
805/437-3198



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Edward 
M. Corrado
Sent: Monday, June 13, 2016 11:30 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Formalizing Code4Lib?

Generally speaking, what the fiduciary agent normally would get rewarded in 
money. Arrangements can vary of course, but basically they would get a portion 
of the income of the event.

Edward

On Mon, Jun 13, 2016 at 1:11 PM, Shaun D. Ellis 
wrote:

> I agree that securing a permanent fiscal agent is the only way to 
> sustain the annual conference at the current level, but I think there 
> are ways to make a less formal commitment.  What I don’t understand is 
> what any fiduciary agent gets out of such a deal.  There is 
> significant risk and overhead for anyone to take this on.  What is the reward?
>
> Overhead
> It’s not just about fronting money and signing contracts.  There is 
> people power involved too.  For 2016, I reviewed every contract and 
> agreement that came through because my hide was on the line if we 
> screwed up.  It’s not hard to miss something in the fine print, or to 
> find estimates and invoices that don’t add up.  Furthermore, there 
> were people in our finance department who had to do extra work to set 
> up the account, cut checks, double-check contracts, communicate with vendors, 
> etc.
>
> Risk
> While we have not yet gone "into the red" on an annual Code4Lib 
> conference (knock on wood), it is certainly possible unless there is a 
> degree of vigilance on the part of the organizers.  Because you have 
> different organizers each year there can be large fluctuations when it 
> comes to fundraising/sponsorship effort and experience.  The same goes 
> for researching, negotiating, and comparing vendor and venue prices.  
> We do pass on documentation as best we can, but the process is rarely 
> cookie cutter.
>
> Reward
> Is the reward simply “thanks” and a pat on the back?  ¯\_(ツ)_/¯  (For 
> what it’s worth, I could see a high-visibility sponsor spot given to 
> this org since it's a form of in-kind donated resources.)
>
> Even if Code4Lib were to form a non-profit to strictly handle the 
> annual conf, someone’s hide needs to be on the line to make sure 
> there’s proper oversight of funds, budgets are properly formed and 
> adhered to, contracts are not putting the org at risk, and so on.  To 
> me, that sounds like a dedicated employee of the non-profit.
>
> -Shaun
>
> On Jun 13, 2016, at 1:30 PM, Rogan Hamby > wrote:
>
> There are a variety of options but I think it's fairly safe to say 
> that it would require some additional organization.  If another body 
> took Code4Lib under it's umbrella they would want organizational 
> contacts and some arrangements in place with whatever served as the 
> governance of Code4Lib (and I use the term governance here very 
> loosely).  And at the other end of the spectrum if Code4Lib did 
> something like become a non-profit there are a number of IRS 
> requirements it would have to observe in terms of a board, bylaws, etc
>
> Note, I'm sure there are other options, those are just the two that 
> occur to me off the top of my head from opposing ends of the "we have 
> to be a formal entity spectrum."
>
> On Mon, Jun 13, 2016 at 12:55 PM, Akerman, Laura > wrote:
>
> Would "finding a permanent fiduciary agent" call for some degree of 
> organizational formalization?  Wouldn't somebody or bodies have to 
> "sign for" Code4Lib on this agreement with this agent, and wouldn't 
> their role therefore have to be, to some degree, permanent?
>
> Sorry, but just wondering...
>
> Laura
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf 
> Of Salazar, Christina
> Sent: Friday, June 10, 2016 5:26 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Yes I think it's time to do so and I also felt that there was 
> significant support for the idea.
>
> I think perhaps the title "formalizing Code4Lib" might be a bit 
> misleading though... We might want to frame the idea as "finding a 
> permanent fiduciary agent" or something along those lines. This way, 
> we don't have to think about major changes all at once.
>
> I imagine it 

[CODE4LIB] Job: Collections Initiative Librarian at University of Tennessee at Chattanooga

[jobs]

Collections Initiative Librarian
University of Tennessee at Chattanooga
Chattanooga

The University of Tennessee at Chattanooga Library seeks an innovative and
dynamic professional for the position of Collections Initiatives Librarian in
the Library's Collection Services Department. Reporting to the Head of
Collection Services, the Collections Initiatives Librarian will assist with
day to day operations across the department, take the lead in our new
scholarly communication initiatives, and lead departmental projects as needed.

  
Full announcement and position description available here:

  
http://www.utc.edu/library/pdfs/admin/collection-initiatives-job-
description.pdf

  
Review of applications begins on June 24, 2016 and continues until position is
filled.



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/26340/
To post a new job please visit http://jobs.code4lib.org/

Re: [CODE4LIB] Formalizing Code4Lib?

[Edward M. Corrado]

Generally speaking, what the fiduciary agent normally would get rewarded in
money. Arrangements can vary of course, but basically they would get a
portion of the income of the event.

Edward

On Mon, Jun 13, 2016 at 1:11 PM, Shaun D. Ellis 
wrote:

> I agree that securing a permanent fiscal agent is the only way to sustain
> the annual conference at the current level, but I think there are ways to
> make a less formal commitment.  What I don’t understand is what any
> fiduciary agent gets out of such a deal.  There is significant risk and
> overhead for anyone to take this on.  What is the reward?
>
> Overhead
> It’s not just about fronting money and signing contracts.  There is people
> power involved too.  For 2016, I reviewed every contract and agreement that
> came through because my hide was on the line if we screwed up.  It’s not
> hard to miss something in the fine print, or to find estimates and invoices
> that don’t add up.  Furthermore, there were people in our finance
> department who had to do extra work to set up the account, cut checks,
> double-check contracts, communicate with vendors, etc.
>
> Risk
> While we have not yet gone "into the red" on an annual Code4Lib conference
> (knock on wood), it is certainly possible unless there is a degree of
> vigilance on the part of the organizers.  Because you have different
> organizers each year there can be large fluctuations when it comes to
> fundraising/sponsorship effort and experience.  The same goes for
> researching, negotiating, and comparing vendor and venue prices.  We do
> pass on documentation as best we can, but the process is rarely cookie
> cutter.
>
> Reward
> Is the reward simply “thanks” and a pat on the back?  ¯\_(ツ)_/¯  (For what
> it’s worth, I could see a high-visibility sponsor spot given to this org
> since it's a form of in-kind donated resources.)
>
> Even if Code4Lib were to form a non-profit to strictly handle the annual
> conf, someone’s hide needs to be on the line to make sure there’s proper
> oversight of funds, budgets are properly formed and adhered to, contracts
> are not putting the org at risk, and so on.  To me, that sounds like a
> dedicated employee of the non-profit.
>
> -Shaun
>
> On Jun 13, 2016, at 1:30 PM, Rogan Hamby > wrote:
>
> There are a variety of options but I think it's fairly safe to say that it
> would require some additional organization.  If another body took Code4Lib
> under it's umbrella they would want organizational contacts and some
> arrangements in place with whatever served as the governance of Code4Lib
> (and I use the term governance here very loosely).  And at the other end of
> the spectrum if Code4Lib did something like become a non-profit there are a
> number of IRS requirements it would have to observe in terms of a board,
> bylaws, etc
>
> Note, I'm sure there are other options, those are just the two that occur
> to me off the top of my head from opposing ends of the "we have to be a
> formal entity spectrum."
>
> On Mon, Jun 13, 2016 at 12:55 PM, Akerman, Laura > wrote:
>
> Would "finding a permanent fiduciary agent" call for some degree of
> organizational formalization?  Wouldn't somebody or bodies have to "sign
> for" Code4Lib on this agreement with this agent, and wouldn't their role
> therefore have to be, to some degree, permanent?
>
> Sorry, but just wondering...
>
> Laura
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Salazar, Christina
> Sent: Friday, June 10, 2016 5:26 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Yes I think it's time to do so and I also felt that there was significant
> support for the idea.
>
> I think perhaps the title "formalizing Code4Lib" might be a bit misleading
> though... We might want to frame the idea as "finding a permanent fiduciary
> agent" or something along those lines. This way, we don't have to think
> about major changes all at once.
>
> I imagine it would help those who plan for Code4Lib 2017 as well, assuming
> that there will be a physical one.
>
> Christina Salazar
> Systems Librarian
> John Spoor Broome Library
> California State University, Channel Islands
> 805/437-3198
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Brian Rogers
> Sent: Friday, June 10, 2016 2:20 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Since the Chattanooga Planning Committee inadvertently prompted this
> newest round of conversations around some degree of formalization, would it
> be useful if we threw together a follow-up survey for the community, to
> test the waters around support (or lack there of) for the notion of
> formalizing, to the extent that it allows for a stable 

[CODE4LIB] On-Premise vs. Cloud Storage for Archival Files

[Brian Rogers]

Hi - looking to speak w/anyone who has shifted from on-premise to cloud storage 
(Glacier, Nearline, Azure, et al) for archival/production master
files. I hope to gain a sense of how workflows were impacted, as well as 
shifting from a "one-time" cost to monthly/annual recurring cost. I imagine I
might have enough questions to warrant a phone call or off-listserv email. 
Thanks in advance (& apologies for cross-posting). - Brian

[CODE4LIB] metadata schema for glossaries?

[diego ferreyra]

Hi, someone knows a metadata schema for glossaries?
sorry about cross posting

tahnk you in advance

-- 
Diego Ferreyra

Re: [CODE4LIB] Formalizing Code4Lib?

[Rogan Hamby]

There are a variety of options but I think it's fairly safe to say that it
would require some additional organization.  If another body took Code4Lib
under it's umbrella they would want organizational contacts and some
arrangements in place with whatever served as the governance of Code4Lib
(and I use the term governance here very loosely).  And at the other end of
the spectrum if Code4Lib did something like become a non-profit there are a
number of IRS requirements it would have to observe in terms of a board,
bylaws, etc

Note, I'm sure there are other options, those are just the two that occur
to me off the top of my head from opposing ends of the "we have to be a
formal entity spectrum."

On Mon, Jun 13, 2016 at 12:55 PM, Akerman, Laura  wrote:

> Would "finding a permanent fiduciary agent" call for some degree of
> organizational formalization?  Wouldn't somebody or bodies have to "sign
> for" Code4Lib on this agreement with this agent, and wouldn't their role
> therefore have to be, to some degree, permanent?
>
> Sorry, but just wondering...
>
> Laura
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Salazar, Christina
> Sent: Friday, June 10, 2016 5:26 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Yes I think it's time to do so and I also felt that there was significant
> support for the idea.
>
> I think perhaps the title "formalizing Code4Lib" might be a bit misleading
> though... We might want to frame the idea as "finding a permanent fiduciary
> agent" or something along those lines. This way, we don't have to think
> about major changes all at once.
>
> I imagine it would help those who plan for Code4Lib 2017 as well, assuming
> that there will be a physical one.
>
> Christina Salazar
> Systems Librarian
> John Spoor Broome Library
> California State University, Channel Islands
> 805/437-3198
>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Brian Rogers
> Sent: Friday, June 10, 2016 2:20 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Formalizing Code4Lib?
>
> Since the Chattanooga Planning Committee inadvertently prompted this
> newest round of conversations around some degree of formalization, would it
> be useful if we threw together a follow-up survey for the community, to
> test the waters around support (or lack there of) for the notion of
> formalizing, to the extent that it allows for a stable place to house the
> annual conference funds? And if it seems like there is overwhelming support
> for the idea, a group of volunteers can band together at that point to
> pursue options to present back to the community?
>
> 
>
> This e-mail message (including any attachments) is for the sole use of
> the intended recipient(s) and may contain confidential and privileged
> information. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this message (including any attachments) is strictly
> prohibited.
>
> If you have received this message in error, please contact
> the sender by reply e-mail message and destroy all copies of the
> original message (including attachments).
>



-- 
--
Rogan R. Hamby, Data and Project Analyst
Equinox - Open Your Library
ro...@esilibrary.com
1-877-OPEN-ILS | www.esilibrary.com

Re: [CODE4LIB] Formalizing Code4Lib?

[Akerman, Laura]

Would "finding a permanent fiduciary agent" call for some degree of 
organizational formalization?  Wouldn't somebody or bodies have to "sign for" 
Code4Lib on this agreement with this agent, and wouldn't their role therefore 
have to be, to some degree, permanent?

Sorry, but just wondering...

Laura

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
Salazar, Christina
Sent: Friday, June 10, 2016 5:26 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Formalizing Code4Lib?

Yes I think it's time to do so and I also felt that there was significant 
support for the idea.

I think perhaps the title "formalizing Code4Lib" might be a bit misleading 
though... We might want to frame the idea as "finding a permanent fiduciary 
agent" or something along those lines. This way, we don't have to think about 
major changes all at once.

I imagine it would help those who plan for Code4Lib 2017 as well, assuming that 
there will be a physical one.

Christina Salazar
Systems Librarian
John Spoor Broome Library
California State University, Channel Islands
805/437-3198


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Brian 
Rogers
Sent: Friday, June 10, 2016 2:20 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Formalizing Code4Lib?

Since the Chattanooga Planning Committee inadvertently prompted this newest 
round of conversations around some degree of formalization, would it be useful 
if we threw together a follow-up survey for the community, to test the waters 
around support (or lack there of) for the notion of formalizing, to the extent 
that it allows for a stable place to house the annual conference funds? And if 
it seems like there is overwhelming support for the idea, a group of volunteers 
can band together at that point to pursue options to present back to the 
community?



This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).

[CODE4LIB] Application Developer at the University of Miami Libraries

[Andrew Darby]

Hello, all.  We’re looking for a developer to join us at the University of
Miami Libraries.   Web & Application Development consists of the department
head, one Digital Preservation & Application Development Librarian, two
programmers (once you join us!), one web designer, and at times a student
worker.  We are responsible, broadly, for all the public interfaces to
library systems, selected backend systems, and for providing application
development and support for our colleagues in the Libraries.  In addition,
we lead user research on web products, and do research and development on
technologies and applications that might be beneficial to the Libraries or
the library community.

*Apply Here: * http://um.hodesiq.com/job_detail.asp?JobID=5230660

The UM Libraries is undergoing a growth spurt in the area of Digital
Strategies, with new hires in GIS Services, Digital Humanities, Data
Scholarship and a Digital Infrastructure Librarian, so we expect a lot of
new and interesting projects to come our way.  We have a couple of existing
open source projects out there (SubjectsPlus [1] and the Remixing Archival
Metadata Project [2]), and are generally a pretty congenial group.

Feel free to drop me a line if you'd like more information.

-- 
Andrew Darby
Head, Web & Application Development
University of Miami Libraries

[1] https://github.com/subjectsplus/SubjectsPlus
[2] https://github.com/UMiamiLibraries/RAMP

[CODE4LIB] Job: Digital Repository Analyst at University of North Carolina at Chapel - corrected url

[Brassell, Emily]

Please excuse the redundant posting, but the link to the job application is 
wrong in the original message.

Here's the corrected link to the application:
https://unc.peopleadmin.com/postings/100361

Thanks!

***

Digital Repository Analyst
University of North Carolina at Chapel Hill
Chapel Hill

The University Library at the University of North Carolina
at Chapel Hill is seeking an applications analyst to join the Carolina Digital
Repository (CDR) Development Team in the Library and Information Technology
directorate to support Open Access initiatives on campus.

Working with CDR development staff, the Analyst designs, implements, tests and
supports software projects at all stages of their lifecycles; evaluates new
technologies and services to implement or customize for use by the UNC
Community; integrates systems and works with established frameworks to support
technology and infrastructure for UNC Open Access initiatives. Given this
focus and the rapidly evolving field of digital scholarship, tasks will be
varied, presenting opportunities to learn new skills and to take on a range of
technically challenging projects with support from senior staff.

The position works with library staff and campus partners to address their
business needs, while coordinating with other developers, system
administrators, project managers and stakeholders; collaborating with
professionals who care about their work, within an environment that respects a
work life balance. The CDR Development group has created graphical
visualizations of repository materials, interactive administrative web
applications, and engaged in rapid prototyping activities in order to respond
to and improve workflows for its users, while also seeking to contribute back
to multiple open-source communities of technologists and professionals.

The Carolina Digital Repository is a digital archive for materials produced by
members of the University of North Carolina at Chapel Hill community. The goal
of the CDR is to preserve and provide access to UNC digital scholarly output
such as publications, data, digitized collections and university records. As
part of the CDR and other projects, the University Libraries are active in and
committed to open source development and communities such as Fedora Commons
Repository.


**Minimum Education and Experience Requirements**

Bachelor's degree in Computer Science, Computer Information Systems, Computer
Engineering, math, or Engineering or related technical degree from an
appropriately accredited institution; or

  * Bachelor's degree and some computer coursework from an appropriately 
accredited institution and one year of experience in business application 
consulting or development; or
  * Associate's degree in Computer Programming and one year of experience in 
application consulting or development; or an equivalent combination of 
education and experience.
  * Journey level requires an additional one year of experience.
  * Advanced level requires an additional two years of experience.

**Essential Skills, Knowledge and Abilities**

The Digital Repository Analyst must have:

  * Experience working collaboratively and communicating effectively with 
stakeholders.
  * Experience developing software with Object Oriented languages.
  * Experience working successfully on a team.
  * Experience with web development.

**Preferred Qualifications**

Experience with Javascript, Ruby on Rails or Java Web Application Development.

  * Comfort with large code bases.
  * Experience integrating with external services and interacting with their 
APIs.
  * Experience with version control (e.g. Git).
  * Experience with agile development methodologies.
  * Experience with RDF and related technologies.
  * Interest/experience in repositories, metadata, and/or preservation.
  * Experience with library repository technologies such as Fedora, Islandora, 
or Hydra.

*Applications**

Closing Date: 06/24/2016

Please visit
https://unc.peopleadmin.com/postings/100361
and complete the online application.

For more information on application procedures, applicants may contact:

Office of Human Resources
University of North Carolina at Chapel Hill
104 Airport Drive CB #1045
Chapel Hill, NC 27514
(919) 843-2300

___
Emily Brassell
ebras...@email.unc.edu | 
ebras...@jabber.unc.edu | 919.962.1356

[CODE4LIB] Job: Digital Repository Analyst at University of North Carolina at Chapel Hill

[jobs]

Digital Repository Analyst
University of North Carolina at Chapel Hill
Chapel Hill

The University Library at the University of North Carolina
at Chapel Hill is seeking an applications analyst to join the Carolina Digital
Repository (CDR) Development Team in the Library and Information Technology
directorate to support Open Access initiatives on campus.

  
Working with CDR development staff, the Analyst designs, implements, tests and
supports software projects at all stages of their lifecycles; evaluates new
technologies and services to implement or customize for use by the UNC
Community; integrates systems and works with established frameworks to support
technology and infrastructure for UNC Open Access initiatives. Given this
focus and the rapidly evolving field of digital scholarship, tasks will be
varied, presenting opportunities to learn new skills and to take on a range of
technically challenging projects with support from senior staff.

  
The position works with library staff and campus partners to address their
business needs, while coordinating with other developers, system
administrators, project managers and stakeholders; collaborating with
professionals who care about their work, within an environment that respects a
work life balance. The CDR Development group has created graphical
visualizations of repository materials, interactive administrative web
applications, and engaged in rapid prototyping activities in order to respond
to and improve workflows for its users, while also seeking to contribute back
to multiple open-source communities of technologists and professionals.

  
The Carolina Digital Repository is a digital archive for materials produced by
members of the University of North Carolina at Chapel Hill community. The goal
of the CDR is to preserve and provide access to UNC digital scholarly output
such as publications, data, digitized collections and university records. As
part of the CDR and other projects, the University Libraries are active in and
committed to open source development and communities such as Fedora Commons
Repository.

  
**Minimum Education and Experience Requirements**  
  
Bachelor's degree in Computer Science, Computer Information Systems, Computer
Engineering, math, or Engineering or related technical degree from an
appropriately accredited institution; or

  * Bachelor's degree and some computer coursework from an appropriately 
accredited institution and one year of experience in business application 
consulting or development; or
  * Associate's degree in Computer Programming and one year of experience in 
application consulting or development; or an equivalent combination of 
education and experience.
  * Journey level requires an additional one year of experience.
  * Advanced level requires an additional two years of experience.
  
**Essential Skills, Knowledge and Abilities**  
  
The Digital Repository Analyst must have:

  * Experience working collaboratively and communicating effectively with 
stakeholders.
  * Experience developing software with Object Oriented languages.
  * Experience working successfully on a team.
  * Experience with web development.
  
**Preferred Qualifications**  
  
Experience with Javascript, Ruby on Rails or Java Web Application Development.

  * Comfort with large code bases.
  * Experience integrating with external services and interacting with their 
APIs.
  * Experience with version control (e.g. Git).
  * Experience with agile development methodologies.
  * Experience with RDF and related technologies.
  * Interest/experience in repositories, metadata, and/or preservation.
  * Experience with library repository technologies such as Fedora, Islandora, 
or Hydra.
  
**Applications  
  
Closing Date:06/24/2016**

  
Please visit

https://unc.peopleadmin.com/hr/postings/100361

and complete the online application.

  
For more information on application procedures, applicants may contact:

  
Office of Human Resources

University of North Carolina at Chapel Hill

104 Airport Drive CB #1045

Chapel Hill, NC 27514

(919) 843-2300



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/26337/
To post a new job please visit http://jobs.code4lib.org/