|
|
| (187 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | <font color="red">'''This procedure assumes that you have used the [[SUNScholar/Dspace|three step process]] to install DSpace.'''</font> | + | <center> |
| | + | '''[[SUNScholar/Customisation|Back to Customisation]]''' |
| | + | </center> |
| | + | ==Introduction== |
| | + | <font color="red">'''It is very important that you ensure that the [[SUNScholar/Clean_URL|repository is properly configured]] so that accurate and authoritative metrics can be accomplished.'''</font> |
| | | | |
| − | =DSpace Google Setup=
| + | The metrics services should be able to reference unique persistent [http://en.wikipedia.org/wiki/Machine-readable_data machine-readable] identifiers and detailed metadata for [[SUNScholar/Open_Access|openly accessible]] digital research artifacts in the repository. |
| − | ==http://scholar.google.com/intl/en/scholar/inclusion.html==
| |
| | | | |
| − | =DSpace Guidelines=
| + | Publishing public data in an open, standard, machine-readable format is a best practice. |
| − | ==https://wiki.duraspace.org/display/DSPACE/Ensuring+your+instance+is+indexed==
| |
| − | ==Analytics==
| |
| − | Open your main Dspace config file and look for the '''xmlui.google.analytics.key''' setting. Enter your google analytics key. Then [[SUNScholar/Rebuild Dspace|rebuild Dspace]].
| |
| − | ==Sitemap==
| |
| − | Frist, edit the DSpace config file and setup sitemaps as follows.
| |
| − | <pre>
| |
| − | #### Sitemap settings #####
| |
| − | # the directory where the generated sitemaps are stored
| |
| − | sitemap.dir = ${dspace.dir}/sitemaps
| |
| | | | |
| − | #
| + | http://www.webcitation.org |
| − | # Comma-separated list of search engine URLs to 'ping' when a new Sitemap has
| |
| − | # been created. Include everything except the Sitemap URL itself (which will
| |
| − | # be URL-encoded and appended to form the actual URL 'pinged').
| |
| − | #
| |
| − | #sitemap.engineurls = http://www.google.com/webmasters/sitemaps/ping?sitemap=http://scholar.sun.ac.za/htmlmap
| |
| | | | |
| − | # Add this to the above parameter if you have an application ID with Yahoo
| + | ==[[SUNScholar/Research Article Metrics|Research Article Metrics]]== |
| − | # (Replace REPLACE_ME with your application ID)
| + | ==[[SUNScholar/Repository Website Metrics|Repository Website Metrics]]== |
| − | # http://search.yahooapis.com/SiteExplorerService/V1/updateNotification?appid=REPLACE_ME&url=
| + | ==[[SUNScholar/References|References]]== |
| − | #
| + | *https://project-thor.readme.io/docs/introduction-to-persistent-identifiers |
| − | # No known Sitemap 'ping' URL for MSN/Live search
| + | *[[Media:Acrl-meaningful-metrics.pdf|2016 - ACRL - MEANINGFUL METRICS]] |
| − | </pre>
| + | *[[Media:Niso-altmetric-best-practice.pdf|2016 - NISO - ALTMETRICS DATA QUALITY CODE OF CONDUCT]] |
| | + | *[[Media:Sparc-briefing-paper-better-analytics.pdf|2015 - SPARC - BETTER WAYS TO EVALUATE RESEARCH AND RESEARCHERS]] |
| | | | |
| − | Second, go to the [http://www.google.com/webmasters Google Webmasters] page and create an account. When asked to submit a sitemap use '''htmlmap''' as the sitemap URL. After the correct setup, you can view your own sitemaps by pointing your browser to:
| + | ==Research Metrics Research== |
| − | http://%my-repository-hostname%/htmlmap
| + | ===Centre for Research on Evaluation, Science and Technology=== |
| − | For example you can view SUNScholar sitemaps by clicking on the link below.
| + | *http://sun025.sun.ac.za/portal/page/portal/Arts/CREST |
| − | http://scholar.sun.ac.za/htmlmap
| |
| | | | |
| − | ==Help== | + | ==Research Assessment Revision== |
| − | * http://www.dspace.org/1_6_2Documentation/ch05.html#N142ED | + | *[[Media:The-leiden-manifesto.pdf|2015 - NATURE - THE LEIDEN MANIFESTO]] |
| − | * http://www.dspace.org/1_5_2Documentation/ch03.html#N10B41 | + | ===San Francisco Declaration on Research Assessment (DORA)=== |
| | + | *http://www.ascb.org/dora |
| | | | |
| − | =Suggestions from the webometrics ranking editors=
| + | [[File:Dora-poster.png|555px]] |
| − | | + | __NOTOC__ |
| − | The role of librarians in the Open Access movement has been very important as they are the main designers, promoters and maintainers of institutional repositories. The basic principles behind the current arrangement of repositories are inspired by the librarianship techniques. However, some decisions guided by these principles are probably hampering the universal adoption of the Open Access initiatives (OAI), as they are ignoring the main users of these repositories: scientists, researchers, scholars. ''We publicly acknowledge the work done by librarians worldwide but we would like to offer some suggestions to improve the impact of the OAI:''
| + | [[Category:Customisation]] |
| − | ==Web address==
| |
| − | The institutional repository is a very important asset of the institution as a whole, not only of the library. We recommend the following syntax for the institutional repository web address:
| |
| − | | |
| − | '''http://repository.university.country'''
| |
| − | (See: http://ir.sun.ac.za/wiki/index.php/Capacity_Planning#Priority_3_-_Digital_asset_indexing_and_hosting)
| |
| − | | |
| − | Collective catalogues are well suited for library purposes, but although harvesters and consortium repositories may be very useful, they should be considered always as secondary systems, mainly for purposes of increasing visibility and searchability. Even for very small institutions it is feasible to set up their own repository that is, as mentioned before, the main research asset for the institution.
| |
| − | | |
| − | ==Web links==
| |
| − | Repositories consist of full text papers, not bibliographic records. That means that the link to the full text file should be clearly marked in the web page of each record. Some repository designs make it difficult to locate such links.
| |
| − | | |
| − | ==URL's and file names==
| |
| − | For scientists it is important that the link to the full text would be easily citable. Therefore the following should be avoided in all situations:
| |
| − | | |
| − | # Very long URLs.
| |
| − | # URLs with nonsense characters that have no meaning. At all times try to include the last name of the first author and the publication year in the URL.
| |
| − | # Files without a suffix indicating the type of file (.pdf, .doc, .ps, etc). Each file must have a suffix.
| |
| − | | |
| − | ==Unique web site==
| |
| − | All the scientific production, formal and informal, draft or definitive, published or unpublished, should be available from a unique web site.
| |
| − | | |
| − | See the following, copied from: http://repositories.webometrics.info/best_practices.html
| |
| − | | |
| − | =Decalogue of good practices in institutional web positioning=
| |
| − | | |
| − | The following recommendations are intended to give some advice to Universities and R&D institutions worldwide in order they have an adequate web presence. Their websites should represent correctly their resources, activities and global performance, providing visitors with a true vision of the institution. We encourage medium and long term projects that give priority to the publication of large volume of quality contents under Open Access type models.
| |
| − | | |
| − | We reject the use of abusive positioning techniques that can generate misleading indicators.
| |
| − | | |
| − | ==URL naming==
| |
| − | | |
| − | Each institution should choose a unique institutional domain that can be used by all the websites of the institution.
| |
| − | | |
| − | It is very important to avoid changing the institutional domain as it can generate confusion and it has a devastating effect on the visibility values.
| |
| − | | |
| − | The alternative or mirror domains should be disregarded even when they redirection to the preferred one.
| |
| − | | |
| − | Use of well known acronyms is correct but the institution should consider including descriptive word, like the name of the city, in the domain name.
| |
| − | | |
| − | ==Create==
| |
| − | | |
| − | A large web presence is made possible only with the effort of a large group of authors. The best way to do that is allowing a large proportion of staff, researchers or graduate students to be potential authors.
| |
| − | | |
| − | A distributed system of authoring can be operative at several levels:
| |
| − | | |
| − | * Central organisation can be responsible of the design guidelines and institutional information
| |
| − | | |
| − | * Libraries, documentation centres and similar services can be responsible of large databases, including bibliographic ones but also large repositories (thesis, pre-prints, and reports)
| |
| − | | |
| − | * Individual persons or teams should maintain their own websites, enriching them with self archiving practices.
| |
| − | | |
| − | Hosting external resources can be interesting for third parties and increase the visibility: Conference websites, software repositories, scientific societies and their publications, especially electronic journals.
| |
| − | | |
| − | ==Convert==
| |
| − | Important resources are available in non electronic format that can be converted to web pages easily. Most of the universities have a long record of activities that can be published in historical web sites.
| |
| − | | |
| − | Other resources are also candidate for conversion, including past activities reports or pictures collections.
| |
| − | | |
| − | ==Interlinking==
| |
| − | | |
| − | The Web is a hypertextual corpus with links connecting pages. If your contents are not known (bad design, limited information, or minority language), the size is scarce or they have low quality, the site probably will receive few links from other sites.
| |
| − | | |
| − | Measuring and classifying the links from others can be insightful. You should expect links from your “natural” partners: Institutions from your locality or region, web directories from similar organisations, portals covering your topics, colleagues or partners personal pages. Your pages should make an impact in your common language community.
| |
| − | | |
| − | Check for the orphaned pages, i.e. pages not linked from another.
| |
| − | | |
| − | ==Language, especially English==
| |
| − | | |
| − | The Web audience is truly global, so you should not think locally. Language versions, especially in English, are mandatory not only for the main pages, but for selected sections and specially from scientific documents.
| |
| − | | |
| − | ==Rich and media files==
| |
| − | | |
| − | Although html is the standard format of web pages, sometimes it is better to use rich file formats like Adobe Acrobat pdf or MS Word doc as they allow a better distribution of documents. PostScript is a popular format in certain areas (physics, engineering, mathematics) but it can be difficult to open, so it is recommended to provide an alternative version in pdf format.
| |
| − | | |
| − | Bandwidth is growing exponentially, so it is a good investment to archive all media materials produced in web repositories. Collections of videos, interviews, presentations, animated graphs, and even digital pictures could be very useful in the long term.
| |
| − | | |
| − | ==Search engine friendly designs==
| |
| − | | |
| − | Avoid cumbersome navigation menus based on Flash, Java or JavaScript that can block the robot access.
| |
| − | Deep nested directories or complex interlinking can block robots too.
| |
| − | | |
| − | Databases and even highly dynamic pages can be invisible for some search engines, so use directories or static pages instead or as an option.
| |
| − | | |
| − | ==Popularity and statistics==
| |
| − | | |
| − | Number of visits is important, but it as much as important to monitor their origin, distribution and the causes why they reach your web sites. Most of the current log analysers offer a great diversity of tables and graphs showing relevant demographic and geographic data, but make sure there is an option to show the referrers, the web pages from which the visit arrives or the search term or phrase used if the visit came from a search engine.
| |
| − | | |
| − | Most popular pages or directories are also relevant.
| |
| − | | |
| − | ==Archiving and persistence==
| |
| − | | |
| − | To maintain a copy of old or outdated material in the site should be mandatory. Sometimes relevant information is lost when the site is redesigned or simply updated and there is no way to recover easily the vanished pages.
| |
| − | | |
| − | ==Standards for enriching sites==
| |
| − | | |
| − | The use of meaningful titles and descriptive metatags can increase the visibility of the pages. There are some standards like Dublin Core that can be used to add authoring info, keywords and other data about the web sites.
| |
| − | | |
| − | =Rankings=
| |
| − | ==[http://repositories.webometrics.info Check your ranking]==
| |
| − | ==[http://roar.eprints.org Check to see who has the most records]==
| |
| − | | |
| − | ==Check the academic rankings==
| |
| − | * http://www.arwu.org
| |
| − | * http://www.webometrics.info
| |
| − | * http://en.wikipedia.org/wiki/College_and_university_rankings
| |
| − | * http://www.topuniversities.com/world-university-rankings
| |
| − | | |
| − | =OAI-PMH=
| |
| − | # Register your site here: http://www.openarchives.org/Register/ValidateSite
| |
| − | # Check first here: http://re.cs.uct.ac.za
| |
| − | | |
| − | The OAI BASE URL's for Stellenbosch University are:
| |
| − | * http://scholar.sun.ac.za/oai/request
| |
| − | * http://etd.sun.ac.za/oai/request
| |
| − | | |
| − | '''[[SUNScholar/IR|Back to IR Help]]'''
| |
