updated README.md
This commit is contained in:
parent
7b4fbd57eb
commit
1ab825ca82
1 changed files with 8 additions and 24 deletions
32
README.md
32
README.md
|
@ -1,27 +1,20 @@
|
|||
# VIVO: Connect, Share, Discover
|
||||
|
||||
VIVO is an open source semantic web application originally developed and implemented at Cornell.
|
||||
When installed and populated with researcher interests, activities, and accomplishments,
|
||||
it enables the discovery of research and scholarship across disciplines at that institution and beyond.
|
||||
VIVO is an open source semantic web tool for research discovery -- finding people and the research they do.
|
||||
|
||||
VIVO supports browsing and a search function which returns faceted results for rapid retrieval
|
||||
of desired information. Content in any local VIVO installation may be maintained manually,
|
||||
brought into VIVO in automated ways from local systems of record
|
||||
(such as HR, grants, course, and faculty activity databases),
|
||||
or from database providers (such as publication aggregators and funding agencies).
|
||||
VIVO supports editing, searching, browsing and visualizing research activity in order to discover people, programs, facilities, funding, scholarly works, and events. VIVO's search returns results faceted by type for rapid retrieval of desired information across disciplines at one institution or, through a prototype at vivosearch.org, across multiple distributed institutions.
|
||||
|
||||
## Resources
|
||||
|
||||
### Information center at VIVOWEB
|
||||
http://vivoweb.org/
|
||||
|
||||
### SoureceForge Wiki:
|
||||
http://sourceforge.net/apps/mediawiki/vivo/index.php?title=Main_Page
|
||||
### DuraSpace Wiki:
|
||||
https://wiki.duraspace.org/display/VIVO/
|
||||
|
||||
## Contact us
|
||||
There are several ways to contact the VIVO community.
|
||||
Use our contact form, send e-mail to the mailing lists, or join the chat room.
|
||||
Whatever your preference, we will be pleased to hear from you.
|
||||
Whatever your interest, we would be pleased to hear from you.
|
||||
|
||||
#### Contact form:
|
||||
http://vivoweb.org/contact
|
||||
|
@ -29,17 +22,17 @@ http://vivoweb.org/contact
|
|||
#### Mailing lists:
|
||||
##### [vivo-dev-all](http://lists.sourceforge.net/lists/listinfo/vivo-dev-all)
|
||||
The best place to get your hands dirty in the VIVO Project.
|
||||
Developers and Implementers frequent this listserv to get the latest on feature design,
|
||||
Developers and implementers frequent this list to get the latest on feature design,
|
||||
development planning, and testing.
|
||||
|
||||
##### [vivo-ontology](http://lists.sourceforge.net/lists/listinfo/vivo-ontology)
|
||||
The VIVO ontology serves as the data model for the VIVO application as well as an
|
||||
The VIVO-ISF ontology serves as the data model for the VIVO application as well as an
|
||||
independent ontology for representing researchers in the context of their
|
||||
experience, outputs, interests, accomplishments, and associated institutions.
|
||||
This list is a place where you can
|
||||
* raise modeling requirements,
|
||||
* share your domain expertise to improve or extend the ontology,
|
||||
* discuss the technical details of the design of the VIVO OWL ontology,
|
||||
* discuss the technical details of the design of the VIVO-ISF ontology,
|
||||
* share general ontology topics and news.
|
||||
|
||||
##### [vivo-imp-issues](http://lists.sourceforge.net/lists/listinfo/vivo-imp-issues)
|
||||
|
@ -47,12 +40,3 @@ Implementing VIVO for the first time? Upgrading to the latest version?
|
|||
This list brings implementers together to help identify and solve questions
|
||||
ranging from installation to best practices.
|
||||
|
||||
#### IRC
|
||||
For instant access to VIVO developers visit the VIVO IRC Channel.
|
||||
VIVO is still a small project so this channel is frequented by developers and end users alike.
|
||||
All are welcome.
|
||||
|
||||
Network: irc.freenode.net
|
||||
Channel: #VIVO
|
||||
WebInterface: http://webchat.freenode.net/
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue