Difference between revisions of "SUNScholar/Capacity Building"

From Libopedia
Jump to navigation Jump to search
m
m
Line 14: Line 14:
 
<center>
 
<center>
 
:<font color="#008000"><big>'''AFTER OPEN ACCESS</big><br><i>No publication fees which adds to funds available for researchers and library budgets</i>'''</font>
 
:<font color="#008000"><big>'''AFTER OPEN ACCESS</big><br><i>No publication fees which adds to funds available for researchers and library budgets</i>'''</font>
</center>
+
 
  
 
[[File:Good.png|480px|center|border|link=http://www.musingsone.com/2014/08/why-are-university-researchers-still.html]]
 
[[File:Good.png|480px|center|border|link=http://www.musingsone.com/2014/08/why-are-university-researchers-still.html]]
Line 25: Line 25:
  
 
  '''[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. Teach a person to fish and you feed that person for a lifetime.]'''
 
  '''[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. Teach a person to fish and you feed that person for a lifetime.]'''
 +
</center>
  
  

Revision as of 11:14, 23 December 2014

Rr-organogram.png

BEFORE OPEN ACCESS
Publication fees that detract from funds available for researchers and library budgets
Bad.png
AFTER OPEN ACCESS
No publication fees which adds to funds available for researchers and library budgets


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



The repository content and the technological systems that run the repository need the following teams to manage and preserve them so that they are always available now and in the far future.

This is the core of the much bigger strategic objectives of (a) the self-hosting value proposition and (b) repository preservation.


The "Systems Team" Skills 
The "Content Team" Skills 

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. One does not expect an administrator to also be a brain surgeon and vice versa. The hospital administrator ensures the smooth functioning of the hospital, for the benefit of the specialists, in order to provide 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 below.

Academic libraries are full of specialists and administrators. Each is professionally trained to fulfil a specific task. Academic repository managers provide a smooth functioning repository with the assistance of the academic repository content librarians and academic repository system administrators (hopefully each becomes professionally trained now and in the future), in order to provide an excellent service to academic 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:

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 be formed for both the "soft" and "hard" skills mentioned above.

Below is more detail about communities of practice.

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

Essential Reading (Only available online)