Brian thinks if url parameters are edited, changes access. When using siteadmin, some actions are not properly checking access rights. Have to figure out what needs to change.
Also highlights gaps in our testing
Anyone interested in addressing this: Brian is willing to explore. Ralph and Andrew are willing to test and possibly help.
VIVO-1918 - i18n: Reload firsttime files on start-up if changed REOPENED
1918 and 1931 blocker tickets were addressed
Work done by Dominik
We need people to review and test for these two tickets so these can be done.
VIVO-1931 - i18n: Page rendering speed with language filtering IN REVIEW
VIVO-1934 - i18n: Limit i18n .ftl files to minimal set IN REVIEW
Ralph: Lets merge it and go!
Michel: Need discussion on the properties file moved to ontology
Andrew: During the sprint call discussed this. One issue is FTL files and templates and associated properties might be too granular. How to make the templates more generalizable? Second issue is how to make the template files into ontology files? Andrew suggests an incremental approach.
Brian: there must be some kind of open source project that can address complex syntax issues. We should look around for other work so not reinventing the wheel.
Ralph: There may be issues adopting other solutions too. He hasn’t seen solutions in JAVA.
Michel: VIVO is a bit unique since semantic application. To generalize variables in FTL file, the ontology can address this. If want to identify other solutions, search through semantic apps.
Andrew: will create ticket for high level refactoring of templates/properties.
This issue also affects the ontology team.
Andrew: We need folks to step up and merge and test the tickets associated with 1918. The work has been done.
1.12 release planning
Code freeze once i18n tickets are merged into the sprint-i18n branch (when?)
We will need a short sprint in order to test the merging of sprint branches to master branch. This happens Jan 25.
Then ready to release a release candidate. This will be available for community testing for 2 weeks. Then put out RC2. Keep going until all bugs addressed.
Feb. would be testing by community. Need Leadership buy-in.
Will schedule work for development team? General agreement.
Need code freeze. When impose on one or both branches? Please continue, will continue conversation next week.
VIVO-1443 - Decouple VIVO build from installation IN REVIEW
Do we want this to be part of 1.12? This addresses the ease of installation.
Rob: Lots of work already done, so should include.
Post-i18n priorities
VIVO-in-a-box
Simplified installation of VIVO
Targeting institutions with limited resources
Would expand number of installations
Based on many conversations with prospective VIVO installations (universities)
Leadership group is currently exploring the opportunity
Functional areas
Data ingest (ReCiter / Web of Science)
Simplified, customizable profile UI
Admin editing UI (TAMU)
Web of Science: don’t forget Dimensions.
Ease of use: Import pictures – need something easy
Data ingest is central.
Most of the technology is there. How to do the least amount of work to get this work.
Don: Don’t forget existing institutions. Maybe we could dovetail with existing data ingest (Ralph)
Reciter is looking promising. Adaptable, generalizable, data ingest tool
Configurability – now need developer for branding.
What are the major tasks?
Ensuring decoupled components
Need to assess cost/benefit of the idea before designing
Most of the components are there... how do we package it?
Thoughts
Would be helpful to have a consistent ingest process
Still will need initial set of faculty info (LDAP)
Indicating note-taker