Difference between revisions of "SUNScholar/Capacity Building"

From Libopedia
Jump to navigation Jump to search
m
m
Line 7: Line 7:
  
 
'''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>'''
 
'''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>'''
−
 
−
'''[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.]'''
 
  
 
  '''<big>[[SUNScholar/Capacity Building/Digital Repository Systems Management|TECHNICAL]]</big>'''
 
  '''<big>[[SUNScholar/Capacity Building/Digital Repository Systems Management|TECHNICAL]]</big>'''
Line 20: Line 18:
 
  '''<span style="color:#76273c">Simplicity is hard to build, easy to use, and hard to charge for.<br>Complexity is easy to build, hard to use, and easy to charge for.</span>'''
 
  '''<span style="color:#76273c">Simplicity is hard to build, easy to use, and hard to charge for.<br>Complexity is easy to build, hard to use, and easy to charge for.</span>'''
  
 +
'''[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.]'''
 
</center>
 
</center>
  

Revision as of 20:20, 29 March 2015

 Back to Guidelines

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) repository preservation and (b) the self-hosting value proposition. 

TECHNICAL

OPERATIONAL

Rr-organogram.png 

Keep it simple, stupid (KISS)

Simplicity is hard to build, easy to use, and hard to charge for.
Complexity is easy to build, hard to use, and easy to charge for.

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.

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 team.

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: 

For more about open services, see: http://wiki.lib.sun.ac.za/index.php/OpenCampus

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://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

News

Tech-perspective.jpg
Retrieved from "http://wiki.lib.sun.ac.za/index.php?title=SUNScholar/Capacity_Building&oldid=34992"