Difference between revisions of "SUNScholar/Capacity Building"

From Libopedia
Jump to navigation Jump to search
m
m
 
(101 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
<center>
 
<center>
  '''[[SUNScholar/Practical guidelines for starting an institutional repository (IR)|Back to Guidelines]]'''
+
'''[[SUNScholar/Practical guidelines for starting an institutional repository (IR)|Back to Guidelines]]'''
 
</center>
 
</center>
 +
;Introduction
 +
In the context of the library, the operational team provides '''[https://infoserviceonto.wordpress.com/2010/06/23/what-is-an-information-service/ information services]''', that are supported by the technical team using '''[https://en.wikipedia.org/wiki/Information_system information systems]''', which are built and maintained in co-operation with the '''[https://en.wikipedia.org/wiki/Information_technology information technology]''' department.
 +
----
 +
'''<big>[[SUNScholar/Capacity Building/Digital Repository Content Management|OPERATIONAL TEAM STRUCTURE AND COMPETENCIES]]</big>'''
  
<center>
+
'''<big>[[SUNScholar/Capacity Building/Digital Repository Systems Management|TECHNICAL TEAM STRUCTURE AND COMPETENCIES]]</big>'''
'''<font color="red">The repository content and the repository infrastructure require the following teams, to ensure that the repository is properly maintained, now and in the far future.'''
 
 
 
'''This is the core of the much bigger strategic objectives of (a) [[SUNScholar/Repository Preservation|repository preservation]] and (b) [[SUNScholar/Self-Hosting_Value_Proposition| the self-hosting value proposition]].</font>'''
 
  
[[File:Rr-organogram.png|555px|border]]
+
----
 +
;What is the difference between the operational and technical teams?
 +
Let me try to explain by way of an analogy using something we are very familiar with, namely property development.
  
'''<big>[[SUNScholar/Capacity Building/Digital Repository Systems Management|TECHNICAL TEAM STRUCTURE AND COMPETENCIES]]</big>'''
+
Property developers buy land prepared with roads and utilities by the local municipality and erect buildings for occupation by future businesses or residents.
  
'''<big>[[SUNScholar/Capacity Building/Digital Repository Content Management|OPERATIONAL TEAM STRUCTURE AND COMPETENCIES]]</big>'''
+
*In the same way the technical team, prepares "roads and utilities" by constructing a "data center" which houses networking and server equipment.
 +
*Then the technical team "erects buildings" by installing software on the servers.
 +
*The software on the servers is utilised by the operational team, the equivalent of "businesses or residents" to complete a specific function.
 +
See links below and above for more information about specific functions of the operational and technical teams.
  
'''[https://en.wikipedia.org/wiki/KISS_principle Keep it simple, stupid (KISS)]'''
+
;What are the functions of these people, with these new job descriptions?
</center>
 
 
 
__TOC__
 
 
 
===<font color="red">What is the difference between the operational and technical teams?</font>===
 
Let me try to explain by way of an analogy using something we are very familiar with, namely property development. Property developers buy land prepared with roads and utilities by the local municipality and erect buildings for occupation by future businesses or residents.
 
 
 
In the same way the technical team, prepares "roads and utilities" by constructing a "data center" which houses networking and server equipment. Then the technical team "erects buildings" by installing software on the servers. The software on the servers is utilised by the operational team, the equivalent of "businesses or residents" to complete a specific function. See links below and above for more information about specific functions of the operational team.
 
 
 
===<font color="red">What are the functions of these people, with these new job descriptions?</font>===
 
 
There seems to be some confusion regarding the role and function of the people described in the links above.
 
There seems to be some confusion regarding the role and function of the people described in the links above.
  
Line 41: Line 37:
 
:*The open scholarship director ensures the smooth functioning of the open academic systems with the assistance of the operational and technical teams, in order to provide an excellent service to researchers.
 
:*The open scholarship director ensures the smooth functioning of the open academic systems with the assistance of the operational and technical teams, in order to provide an excellent service to researchers.
  
===<font color="red">What else can these teams do for the library and the institution?</font>===
+
;What else can these teams do for the library and the institution?
 
These same teams, with their skills, are also then capable of enabling other open systems for the institution, for example:
 
These same teams, with their skills, are also then capable of enabling other open systems for the institution, for example:
 
*[http://journals.sun.ac.za An open journal system]
 
*[http://journals.sun.ac.za An open journal system]
Line 51: Line 47:
 
*[[OpenCampus/Library|An open library management system]]
 
*[[OpenCampus/Library|An open library management system]]
  
'''For more about open services, see: http://wiki.lib.sun.ac.za/index.php/OpenCampus'''
+
;Communities of Practice (CoP)
 
 
===Communities of Practice (CoP)===
 
 
In lieu of the lack of professional training venues for open online scholarly publishing practice, it is suggested that [http://en.wikipedia.org/wiki/Community_of_practice communities of practice] (CoP) be formed for both the "soft" and "hard" skills mentioned above.
 
In lieu of the lack of professional training venues for open online scholarly publishing practice, it is suggested that [http://en.wikipedia.org/wiki/Community_of_practice communities of practice] (CoP) be formed for both the "soft" and "hard" skills mentioned above.
  
Line 76: Line 70:
 
  http://www.arl.org/focus-areas/shared-access-research-ecosystem-share
 
  http://www.arl.org/focus-areas/shared-access-research-ecosystem-share
  
===Scholarly Publishing Links===
+
;Scholarly Publishing Links
 +
http://jlsc-pub.org
 
  http://www.journalofelectronicpublishing.org
 
  http://www.journalofelectronicpublishing.org
 
  http://www.openaccesspublishing.org
 
  http://www.openaccesspublishing.org
Line 86: Line 81:
 
  http://www.aaupnet.org
 
  http://www.aaupnet.org
  
===[[SUNScholar/Essential Reading|References]]===
+
;[[SUNScholar/References|References]]
*[http://wiki.lib.sun.ac.za/images/f/f6/2015-principle-for-open-scholary-communication-infrastructures.pdf 2015 - NEYLON - PRINCIPLES OF OPEN SCHOLARLY COMMUNICATIONS INFRASTRUCTURE]
+
Click on the heading above for further references.
*[[Media:2015-acrl-libraries-as-publishers.pdf|2015 - ACRL - LIBRARIES AS PUBLISHERS]]
+
*[[Media:Capacity-building.pdf|2016 - HGIBSON - CAPACITY BUILDING FOR SUSTAINABLE DIGITAL INFORMATION SERVICES IN AN ACADEMIC LIBRARY]]
*[[Media:Civ15i4on.pdf|2015 - CRAWFORD - THE ECONOMICS OF OPEN ACCESS]]
+
*[http://staff.lib.sun.ac.za/~hgibson 2016 - HGIBSON - AN INTRODUCTION TO THE PRESERVATION OF THE SCHOLARY COMMUNICATION RECORD BY ACADEMIC LIBRARIES]
*[[Media:OSI-report-Feb-2015.pdf|2015 - OSI - MAPPING THE FUTURE OF SCHOLARLY PUBLISHING]]
+
*[[Media:IAPDigitalknowledgeproceedingsMay2009.pdf|2009 - IAP - PROGRAMME ON DIGITAL KNOWLEDGE RESOURCES AND INFRASTRUCTURE IN DEVELOPING COUNTRIES]]
----
+
*[http://www.interacademies.net/10878/13925.aspx 2003 - IAP - STATEMENT ON SCIENTIFIC CAPACITY BUILDING]
*[[Media:2014-brembs-scholarly-infrastructure.pptx|2014 - BREMBS - THE DESOLATE STATE OF OUR SCHOLARLY INFRASTRUCTURE]]
+
;Jobs
*[[Media:2014-steele-scholary-comm.pdf|2014  - STEELE - SCHOLARLY COMMUNICATION, SCHOLARLY PUBLISHING AND UNIVERSITY LIBRARIES]]
+
*http://tagteam.harvard.edu/hubs/oatp/tag/oa.jobs
*[[Media:New-approaches-in_library-based-publishing.mp4|2014 - SWAN - NEW APPROACHES IN LIBRARY BASED PUBLISHING]]
 
*[https://www.coar-repositories.org/activities/support-and-training/task-force-competencies/ 2014 -  COAR - TASK FORCE: LIBRARIAN COMPETENCIES FOR SCHOLARLY COMMUNICATIONS PUBLISHING]
 
*[[Media:Aligning-Repository-Networks-Meeting-Report.pdf|2014 - COAR - TOWARD A SEAMLESS GLOBAL INFRASTRUCTURE FOR REPOSITORIES]]
 
*[[Media:2014-skinner-library-as-publisher.pdf|2014 - SKINNER - LIBRARY-AS-PUBLISHER: CAPACITY BUILDING FOR THE LIBRARY PUBLISHING SUBFIELD]]
 
*[[Media:2014-mangiafico-models-for-libraries.pdf|2014 - MANGIAFICO - MODELS FOR LIBRARIES IN AN EVOLVING SCHOLARLY PUBLISHING ECOSYSTEM]]
 
*[[Media:2014-raju-skills.pdf|2014 - RAJU - KNOWLEDGE AND SKILLS FOR THE DIGITAL ERA ACADEMIC LIBRARY]]
 
*[[Media:Niso-isq-2014-oa.pdf|2014 - NISO - OPEN ACCESS INFRASTRUCTURE]]
 
*[http://blog.martinfenner.org/2014/07/24/dont-reinvent-the-wheel 2014 - MF - DON'T REINVENT THE WHEEL]
 
*[http://blog.martinfenner.org/2014/07/18/roads-not-stagecoaches 2014 - MF - BUILD ROADS NOT STAGECOACHES]
 
*[http://crln.acrl.org/content/75/4/187.full 2014 - ARL - DEVELOPING DIGITAL SCHOLARSHIP SERVICES ON A SHOESTRING BUDGET]
 
*[[Media:Lpc-launch.pdf|2014 - LIBRARY PUBLISHING COALITION LAUNCHED]]
 
*[[Media:Alia-future-libraries.pdf|2014 - ALIA - FUTURE OF LIBRARIES AS PUBLISHERS]]
 
*[[Media:Infrastructuresforopendigitalscience-140512050454-phpapp01.ppt|2014 - EC - INFRASTRUCTURES FOR OPEN DIGITAL SCIENCE]]
 
*[[Media:Open-standards-and-the-digital-age.pdf|2014 - PRWEB - OPEN STANDARDS AND THE DIGITAL AGE]]
 
*[[Media:Oa-proposal-sustainable.pdf|2014 - KN - A SCALABLE AND SUSTAINABLE APPROACH TO OPEN ACCESS PUBLISHING]]
 
*[[Media:WEF_GlobalInformationTechnology_Report_2014.pdf|2014 - WEF - STATE OF INFORMATION TECHNOLOGY REPORT 2014]]
 
*[http://uk.akamai.com/stateoftheinternet 2014 - AKAMI - STATE OF THE INTERNET REPORT]
 
----
 
*[http://wiki.lib.sun.ac.za/images/c/c2/2013-architecting-the-future-of-scholarly-communication.pdf 2013 - NEYLON - ARCHITECTING THE FUTURE OF SCHOLARLY COMMUNICATIONS]
 
*[[Media:Osswatch-survey-2013.pdf|2013 - OSSWATCH - NATIONAL SOFTWARE SURVEY]]
 
*[[Media:A-vision-for-osc-infrastructure.pdf|2013 - DLIB - A VISION TOWARDS SCIENTIFIC COMMUNICATION INFRASTRUCTURES]]
 
*[[Media:Idrc-connecting-ict-to-development.pdf|2013 - IDRC - CONNECTING ICT TO DEVELOPMENT]]
 
*[[Media:Mdpi.pdf|2013 - MDPI - THE IMPORTANCE OF OPEN SOURCE SOFTWARE AND STANDARDS IN MODERN SCIENTIFIC PUBLISHING]]
 
*[[Media:LibraryPressCollaboration report.pdf|2013 - AAUPNET - LIBRARY AND UNIVERSITY PRESS COLLABORATION]]
 
*[[Media:Affordability-report-2013.pdf|2013 - A4AI - INTERNET AFFORDABILITY REPORT]]
 
*[[Media:Doc-bb-policy.pdf|2013 - DEPARTMENT OF COMMUNICATIONS - SOUTH AFRICA - BROADBAND POLICY]]
 
*[[Media:Era_progress_report2013.pdf|2013 - EU - EUROPEAN RESEARCH AREA (ERA) PROGRESS REPORT]]
 
*[[Media:LibraryPressCollaboration report.pdf|2013 - AAUPNET - LIBRARY AND UNIVERSITY PRESS COLLABORATION]]
 
----
 
*[[Media:22-steps-to-an-open-access-research-repository.pdf|2012 - EIFL - IRYNA KUCHMA - 22 STEPS TO AN OPEN ACCESS RESEARCH REPOSITORY]]
 
*[[Media:2012-jlsc-simmons-new-roles-examining-training-needs-of-repository-staff.pdf|2012 - JLSC - SIMMONS - NEW ROLES AND RESPONSIBILITIES: EXAMINING TRAINING NEEDS OF REPOSITORY STAFF]]
 
*[[BOAI/Section3#3.8|2012 - BOAI - ON INFRASTRUCTURE AND SUSTAINABILITY]]
 
*[[Media:Purdue-library-publishing-services-strategies-for-success-final.pdf|2012 - PURDUE UNIVERSITY - STRATEGIES FOR LIBRARY PUBLISHING SUCCESS]]
 
----
 
*[[Media:2011-perry-the-balance-point.pdf|2011 - PERRY - THE BALANCE POINT]]
 
*[[Media:Repository Staff and Skills Set 2011.pdf|2011 - RSP UK - REPOSITORY STAFF AND SKILL SET]]
 
*[[Media:TCO-of-OSS.pdf|2011 - LSE - TOTAL COST OF OWNERSHIP OF OPEN SOURCE SOFTWARE]]
 
----
 
*[[Media:Driver-and-coar.pdf|2009 - UMINHO - DRIVER AND COAR - FROM INFRASTRUCTURE TO CONFEDERATION]]
 
*[[Media:Sparc-oa-income-models.pdf|2009 - SPARC - OPEN ACCESS INCOME MODELS - CURRENT PRACTICE]]
 
----
 
*[[Media:Oa-oss-willinsky.pdf|2005 - WILLINSKY - CONVERGENCE OF OPEN ACCESS, OPEN SOURCE AND OPEN SCIENCE]]
 
----
 
*[[Media:Michael Gorman - Five new laws of librarianship.pdf|1995 - MICHAEL GORMAN - FIVE NEW LAWS OF LIBRARIANSHIP]]
 
----
 
*[[Media:Boyer.pdf|1990 - BOYER - SCHOLARSHIP RECONSIDERED - PRIORITIES OF THE PROFESSORIATE]]
 
  
===News===
+
;News
 
*http://www.newindianexpress.com/education/edex/Libraries-in-The-Technology-Age/2014/12/29/article2589861.ece
 
*http://www.newindianexpress.com/education/edex/Libraries-in-The-Technology-Age/2014/12/29/article2589861.ece
 
*http://www.desmoinesregister.com/story/news/education/2014/12/28/harrison-inefuku-builds-iowa-state-digital-repository/20978135/
 
*http://www.desmoinesregister.com/story/news/education/2014/12/28/harrison-inefuku-builds-iowa-state-digital-repository/20978135/
  
[[File:Tech-perspective.jpg|center|border|666px]]
+
;References
 +
*https://www.coar-repositories.org/activities/support-and-training/task-force-competencies
 +
*http://www.arl.org/focus-areas/scholarly-communication/digital-scholarship-support
 +
<center>
 +
'''[https://en.wiktionary.org/wiki/give_a_man_a_fish_and_you_feed_him_for_a_day;_teach_a_man_to_fish_and_you_feed_him_for_a_lifetime Give a person a fish and you feed that person for a day.<br>Teach a person to fish and you feed that person for a lifetime.]'''
 +
 
 +
'''<span style="color:red">Complexity is easy to build, hard to use, and easy to charge for.<br>Simplicity is hard to build, easy to use, and hard to charge for.</span>'''
 +
 
 +
[[File:Digital-dividends.png|444px|center|border]]
 +
 
 +
[[File:Slhe.png|444px|center|border|link=http://wiki.lib.sun.ac.za/images/e/ec/Slhe.pdf]]
 +
 
 +
[[File:5-laws-modern.png|444px|center|border|link=http://wiki.lib.sun.ac.za/images/1/17/Michael_Gorman_-_Five_new_laws_of_librarianship.pdf]]
 +
 
 +
[[File:Bullshit.jpg|border|444px|center|border|link=http://www.iflscience.com/editors-blog/acceptance-profound-sounding-bs-linked-lower-intelligence]]
 +
 
 +
[[File:Uk-capacity-planning.jpg|444px|center|border]]
 +
</center>
 +
__NOTOC__
 +
[[Category:Operations]]

Latest revision as of 14:08, 1 December 2016

Back to Guidelines
Introduction

In the context of the library, the operational team provides information services, that are supported by the technical team using information systems, which are built and maintained in co-operation with the information technology department.


OPERATIONAL TEAM STRUCTURE AND COMPETENCIES

TECHNICAL TEAM STRUCTURE AND COMPETENCIES


What is the difference between the operational and technical teams?

Let me try to explain by way of an analogy using something we are very familiar with, namely property development.

Property developers buy land prepared with roads and utilities by the local municipality and erect buildings for occupation by future businesses or residents.

  • In the same way the technical team, prepares "roads and utilities" by constructing a "data center" which houses networking and server equipment.
  • Then the technical team "erects buildings" by installing software on the servers.
  • The software on the servers is utilised by the operational team, the equivalent of "businesses or residents" to complete a specific function.

See links below and above for more information about specific functions of the operational and technical teams.

What are the functions of these people, with these new job descriptions?

There seems to be some confusion regarding the role and function of the people described in the links above.

Let me try to explain by way an analogy, using the medical services field as an example..

  • Hospitals are full of specialists and administrators.
  • Each is professionally trained to fulfil a specific task.
  • The hospital administrator ensures the smooth functioning of the hospital, for the benefit of the specialists, in order to provide an excellent service to patients.

So it is, with the greatly expanded and currently expanding, technology and information sciences fields, in that, more specialisation is becoming the norm, as it was and is, in the medical field.

And now an attempt to translate the medical services definition to a library services definition, in support of academic research publishing and archiving.

  • Academic libraries are full of librarians and directors.
  • Each is professionally trained to fulfil a specific task.
  • The open scholarship director ensures the smooth functioning of the open academic systems with the assistance of the operational and technical teams, in order to provide an excellent service to researchers.
What else can these teams do for the library and the institution?

These same teams, with their skills, are also then capable of enabling other open systems for the institution, for example:

Communities of Practice (CoP)

In lieu of the lack of professional training venues for open online scholarly publishing practice, it is suggested that communities of practice (CoP) be formed for both the "soft" and "hard" skills mentioned above.

Below is a brief introduction to communities of practice.

Below are some web site examples.

http://www.force11.org
http://adlsn.org
http://www.itoca.org
http://open-access.org.uk
http://openaccess.jiscinvolve.org
http://is4oa.org
http://aoasg.org.au
https://www.openaire.eu
http://chorusaccess.org
http://www.driver-community.eu
http://www.medoanet.eu
http://www.libereurope.eu/committee/scholarly-research
https://www.coar-repositories.org/activities/repository-interoperability
http://www.arl.org/focus-areas/shared-access-research-ecosystem-share
Scholarly Publishing Links
http://jlsc-pub.org
http://www.journalofelectronicpublishing.org
http://www.openaccesspublishing.org
http://www.librarypublishing.org
http://hybridpublishing.org
http://www.pubs-for-dev.info
http://www.sparc.arl.org/theme/campus-based-publishing
http://www.sspnet.org
http://www.aaupnet.org
References

Click on the heading above for further references.

Jobs
News
References
Give a person a fish and you feed that person for a day.
Teach a person to fish and you feed that person for a lifetime.
Complexity is easy to build, hard to use, and easy to charge for.
Simplicity is hard to build, easy to use, and hard to charge for.
Digital-dividends.png
Slhe.png
5-laws-modern.png
Bullshit.jpg
Uk-capacity-planning.jpg