Date: Fri, 29 Mar 2024 03:38:02 -0400 (EDT)
Message-ID: <801408523.29998.1711697882541@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_29997_312579033.1711697882541"
------=_Part_29997_312579033.1711697882541
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Calls are held every Thursday at 1 pm eastern daylight time (GMT=
-5) =E2=80=93 convert to your time at http://www.thetimezonec=
onverter.com
Please add additional agenda items or updates =E2=80=93 we alway=
s welcome suggestions
Updates
- Weill Cornell =E2=80=93 1) Thanks to Vincent of UFL for consultation on=
implementing Shibboleth. Surprising behavior asking users with no profiles=
to create a VIVO account. Possible to suppress this feature? Jim will =
look at where the account creation is triggered and confer with Eliza about=
the options Weill would prefer. Note that the code does not create a profi=
le, just a user account. 2) Problems encoding special characters durin=
g PubMed Harvester ingest. Data (vivo-additions.rdf.xml) seem properly enco=
ded. Just not sure why the encoding couldn't make it to VIVO. e.g. should i=
t be =CE=B2 or =CE=B2 in the vivo-additions.rdf.xml file? It may be nec=
essary to add a method in the harvester to read in the additions file and c=
onvert any Latin-1 (ISO-8859-1) characters to UTF8 =E2=80=93 Stephen indica=
ted UF would look into whether there is the same issue at UF that had just =
not been detected yet, or whether there's a difference in default character=
sets between the Mac (Weill) and Linux (UF).
- Colorado =E2=80=93 have been meeting with their Laboratory for Atmo=
sphere and Space Physics (LASP), who are interested in running VIVO but add=
ing additional detail about instrumentation including satellites. Stella he=
lped out with questions at one of the meetings. Otherwise evaluating 1.5 to=
see about when to update.
- Florida =E2=80=93 finishing up the people harvest using biztalk mes=
sages for updates instead of database access; the harvester team is looking=
at 3 possible ways to reduce memory usage in the harvester =E2=80=93 upgra=
ding jena, changing the jenaconnect query to bring back only a subset of th=
e VIVO data model, and testing to see whether SDB's performance is fast eno=
ugh that the harvester can query dynamically for scoring and other purposes=
. They will want to work with Cornell on how they might leverage the RDF AP=
I in v1.5. It would be appealing to add a connection to a SPARQL endpoint a=
s a new type of datasource for the harvester.
- Duke =E2=80=93 has their hiding feature in test; this allows a pers=
on to remove any unwanted data from their profile. The data are removed fro=
m VIVO but the identifier in the source system is stored in a hides table a=
nd consulted with each subsequent data load. Enough information is stored w=
ith the hidden identifier to offer the profile editor a choice of bringing =
the data back, at which time new data is fetched from the appropriate sourc=
e system of record. Duke is also testing ingest of data from Symplectic Ele=
ments via their library, and will be working on areas of interest next mont=
h; Pat Gamsby has been in touch with Jon about coordinating with Cornell an=
d potentially Colorado
Release 1.5
- Still tracking down links and references to 1.4 on the wiki, vivoweb.or=
g, and sourceforge =E2=80=93 and we welcome help welcome in identifying mis=
sing documentation and/or outdated links
- Collecting issues for a VIVO 1.5.1 maintenance update=20
- Vitro installation guide
- new data property default list view files in the VIVO productMod but no=
t Vitro
- please notify us of other bugs and/or omissions and confusing or missin=
g documentation=20
- need to make instructions for adding HTML menu pages clearer =E2=80=
=93 if the desired HTML is in the custom template already, there's no need =
to put HTML into the page management form, but the field is required to be =
non-empty on the form. This will be fixed in 1.5.1, but for now it would wo=
rk to just put a tag into the form to make the validation work
Conference planning=
h1>
- Schedule very close to being finalized and released
- Taking proposals for BOF sessions
- Seeking session moderators
- Will be asking all implementing sites to prepare a simple poster using =
(optionally) a provided template to minimize the work required =E2=80=93 em=
phasizing that these do not have to represent completed work or public prod=
uction VIVO instances. There will be a lot of interest at the conference in=
seeing the full range of VIVO projects, no matter how new and exploratory.=
Notable De=
velopment List Traffic
- Developer =
documentation and codebase from the=
Melbourne Central Research Data Registry, prepared by Tom Sullivan and Jud=
d Kirby of [jksoftware.com.au JK Software=
span>]
- building the DV Docs code locally (see also How to implement a Digital Vita CV and biosketch web service for VI=
VO Eliza recommends downloading the XSPARQL Jar files from the Digi=
tal Vita repository rather than recompiling them locally
- referencing profile photos across sites - Jim has been in touch wit=
h Tammy
- VIVO Harvester install docs not clear on connecting to VIVO with 1.4 ch=
anges =E2=80=93 Chris Haines has been working with Jess Meek and Stephe=
n will check in to see whether additional questions or issues remain=
li>
- VIVO with Fuseki SPARQL endpoint =E2=80=93 Vince sent a link to the=
full Fuseki package with all of=
the jars and files that are required. If this tar file is extracted to a l=
ocation, it has a service script and shell script for starting it automatic=
ally.
- 1.5 page management =E2=80=93 Tim Worrall worked this out with Tamm=
y =E2=80=93 if the HTML for a menu page is in the custom page template alre=
ady, it's only necessary to put anything in the HTML field on the 'add menu=
page' form because of form validation; we can fix that with 1.5.1
- VIVO at Eindhoven University of Technology and a Youtube video of a research output discovery application based =
on that VIVO installation
- options for migrating off the SourceForge hosted wiki
- the larger question of whether and when to move to Github (possible gue=
st speaker from Github in the next few weeks)
1. Please join my meeting. https://www1.gotomeetin=
g.com/join/322087560
2. Use your microphone and speakers (VoIP) - a headset is recommended. O=
r, call in using your telephone.
Dial +1 (773) 897-3008
Access Code: 322-087-560
Audio PIN: Shown after joining the meeting
Meeting ID: 322-087-560
last meeting | <=
a href=3D"/display/VIVO/Development+Call+20120726">next meeting
------=_Part_29997_312579033.1711697882541--