You are viewing an old version of this page. View the current version .
Compare with Current
View Page History
« Previous
Version 2
Next »
Date 23 Apr 2019
Time: 11:00 am, Eastern Time (New York, GMT-05:00)
To join the online meeting:
Slack Attendees Indicating note-taker
Don Elsborg Huda Khan Ralph O'Flinn Andrew Woods Steven McCauley Harry Thakkar Agenda TAMU Scholars Demo
Texas A&M University will be demonstrating work that has been completed on their replacement for the VIVO user interface front end (T AMU Scholars ). This replacement front end is based on Solr , Spring Data , and Angular Universal . The basic goals of this front end are:
Align the technology stack as much as possible with the existing VIVO stack to assist with ease of implementation by others if they choose especially smaller libraries. Read only UI.
NO updating back to the triple store.
100% Search Engine Optimization. IE: A person / crawler does not need JavaScript enabled for page rendering. Server side, and Client side rendering if needed.
TAMU Scholars follows much of the same ideas of the VIVO Scholars Task Force but with a slightly different technology stack. (GitHub Repo )Status of In-Review tickets
Click here to expand...
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Soft balls
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Low-hanging, documentation - Mike Conlon , can you give this one a review? Regular balls
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
New
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Kitio Fofack ? Orcid and i18n
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Is this feature of broader interest?
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Andrew Woods to look into
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Mostly trivial, with conversation around Tomcat version support
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Kitio Fofack to review? Received
Click here to expand...
Click here to expand...
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
(re-)Raises interest in reconsidering first-time, every-time, tdbconfig design
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Should be low-hanging
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Where does this stand? What is needed to add more person identifiers to VIVO?
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Mike Conlon : thoughts on where this stands?Bugs (1.11)
Click here to expand...
type
key
summary
assignee
reporter
priority
status
resolution
created
updated
due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Notes Draft notes in Google-Doc
Actions
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Mike Conlon , can you give this one a review?Previous Actions