...
- Sprint updates - i18n
- discuss potential methods for external consumers like VIVO Scholars to query/harvest data from an i8n i18n VIVO
- sprint details
- vivo-tech emails
- Missing N3-PP writer and RiotException -
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1761 - How to remove people from Vivo - two solutions are being suggested... could someone create JIRA tickets?
- > a nice feature in the UI would be a deletion option that allows you to delete the primary object, plus whatever else is created via the UI when you create a new object. It could re-use the logic in the form controller
- > Another possibility would be an automatic deletion of orphan objects: vcards without individuals, publications without authors, and for us membership without members. This could take place synchronously or asynchronously, through a script
- Missing N3-PP writer and RiotException -
- Vitro JMS messaging approaches
- Moving tickets forward
- back on your plate, Mike ConlonJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658
- Who is working on what?
- no progress since last weekJira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1443
- ease of installation is vital, anyone interested?Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752
- Using community questions to lift the entire team
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1749 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1750
- Incremental development initiatives
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1688 Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1751 - Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1752
...