...
- Performance
- Installation and testing
- Site and page management
- Support for sameAs
- Web service for the RDF API
- Serialize/restore graphs in quad format
- Editing
- Ingest tools
- Internationalization
- Provenance
- Visualization
- Data query, export and reporting
- CV generation
- Search indexing
- Modularity
- Ontology
- Tools outside VIVO
...
The following proposed features are not in priority or temporal order.
Please put other ideas here, even tentative suggestions
| Anchor | ||||
|---|---|---|---|---|
|
...
Griffith University has implemented page caching and Arve Solland gave a talk on this and other aspects of the Griffith Research Hub at the 2012 VIVO conference.
| Anchor | ||||
|---|---|---|---|---|
|
There are also other ways to address performance that could be argued are more effective in the long run
...
- Brian Caruso has proposed adding a unit test for Solr that would build an index from a standard set of VIVO RDF, start Solr, and run standard searches. This would help prevent breaking existing functionality when addressing issues that have come up such as support for diacritics, stop words, and capital letters in the middle of names
- A unit test has been developed for another related project at Cornell and we hope to be able to port this to VIVO, but perhaps not for 1.6
Jira server DuraSpace JIRA key VIVO-102
- Developing
(not for 1.6) Developing repeatable tests of loading one or more large datasets into VIVO. The challenge here is that performance is highly installation dependent. The most urgent problem at Cornell has been the intermittent loss of communication between the VIVO web server and the VIVO database server, which results in some threads of activity simply hanging and never returning. As with many errors that are hard to reproduce, we have developed workarounds that divide large jobs into chunks of data that experience has shown can be removed or added without causing hiccups. Stay tuned.
...
- Joe M. has submitted a paper to the Conference on a data ingest method using a standard set of data. This could conceivably be extended to serve as a set of tests, but is presently more geared toward helping people new to VIVO understand data ingest than testing VIVO under load
| Anchor | ||||
|---|---|---|---|---|
|
- Make the About Make the About page HTML content editable through admin interface – this relates to display model changes
Jira server DuraSpace JIRA key VIVO-105 - Note that the home page cannot be made editable through the admin interface as it is too complex
Offering improved options for content on the home page, including a set of SPARQL queries to highlight research areas, international focus, or most recent publicationsJira server DuraSpace JIRA key VIVO-106
- Offering additional individual page template options
Jira server DuraSpace JIRA key VIVO-107 - Document the screen capture configuration as part of this
- could put the service-specific aspects in a sub-template that gets imported and could be default not attempt to capture and cache images at all
- are free services out there, but they may not be there in 6 months
- Offering the ability to embed SPARQL query results in individual pages on a per-class basis – for example, to show all research areas represented in an academic department
Jira server DuraSpace JIRA key VIVO-108
...
Jira server DuraSpace JIRA key VIVO-101 - Implementing a web service interface (with authentication) to the VIVO RDF API, to allow the Harvester and other tools to add/remove data from VIVO and trigger appropriate search indexing and recomputing of inferences.
Authentication will be involved- This would also enable round-trip editing of VIVO content from Drupal or another tool external to VIVO via the SPARQL update capability of the RDF api
- Put and delete of data via LOD requests – this has been suggested but we're not sure a specification even exists for an LOD "put" request – please add references here if you're aware of discussion or documentation.
- Authentication will be involved
- Could manage in our own authentication and authorization system and tell Apache that the servlet requires an HTTPS connection
- This approach would allow testing in a known environment without having to set up SSL certificates
- It would help the user experience if it's possible to bundle together an atomic change set (at least all those changes for one graph), so additions and retractions would not show up piecemeal
- Note that since inferences are done is a separate thread there may still be some lag
- Put and delete of data via LOD requests – this has been suggested but we're not sure a specification even exists for an LOD "put" request – please add references here if you're aware of discussion or documentation.
| Anchor | ||||
|---|---|---|---|---|
|
Jira server DuraSpace JIRA key VIVO-23
| Anchor | ||||
|---|---|---|---|---|
|
...