Date: Fri, 29 Mar 2024 11:58:44 -0400 (EDT) Message-ID: <372228157.316.1711727924401@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_315_56499648.1711727924401" ------=_Part_315_56499648.1711727924401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
View and edit this page permanently at https://wiki.d= uraspace.org/x/r-AQAg, or use the temporal Google Doc f= or collaborative note taking during the call.
DuraSpace is seeking a dynamic and entrepreneurial Project Director for = the open source VIVO project (www.vivoweb.org= a>), a world-wide community focused on creating software tools, ontologies,= and services. The VIVO Project Director will have the opportunity to play = a major role in a collaborative movement that will shape the future of rese= arch.
Report on merging the dev-ISF branch into the main dev branch (in progre= ss)
Full-scale testing should begin week = after next
Notes from Sept. 10 meeting and WebCast: www.youtube.com/watch?v=3D9-95XzYs8ME
Next meeting (timed for international attendance): = ;Tuesday, September 24 at 8 AM Eastern, 10 pm Melbourne, 1 pm London, 2pm A= msterdam and Rome
Colorado (Alex) -- still making p= rogress on Elements curation despite recent flooding issues in the area; tr= ying to get publications information brought into their faculty reporting t= ool as part of the annual reporting process so that the faculty can review = the data for correctness at the same time they do other updates; publicatio= ns would come over to VIVO in early 2014.
Cornell (Jon, Tim, Huda, BrianL) = -- working on the release =E2=80=A6 have an Elements instance up with their= people in it, starting to explore it
Duke (Sheri & Patrick) We con= tinue to develop a feature to load artistic works. Have been trying t= o configure Elements so that data entry will take place there, and we will = use our existing framework to import artistic relationships and works. We= =E2=80=99re now considering other alternatives however because Elements has= the =E2=80=98role=E2=80=99 attribute on the artistic work. We need r= ole to be on the relationship. If we are unable to add custom fields = to the relationship in Elements, we will not be able to use Elements for th= e artistic works feature and would have to develop another system for that = data entry. We=E2=80=99re also modifying our grant import process to = present a larger set - we have significantly restricted the number of grant= s we load into Vivo because we need to be careful not to import those that = should not be publicized.
Can manipulate the data from Elem= ents as bring it across, but because the role is on the work, everybody con= nected to a publication would be assigned the same role. Need roles beyond = the current author, editor, and translator supported in Elements.
Would be good to bring up on the = Symplectic North American user forum
Colorado is working with Elements= but so far has been focusing on more standard publication types
=EPA (Zac) -- Cleaning up data and= waiting for approval to release. Nothing new. Have a system that runs HR u= pdates that are trying to wire up so changes get propagated to VIVO.=
Florida (Nicholas and Chris)
URL rewrite from http://vivo.ufl.edu/display/cpb
to http://vivo.ufl.edu/display/n64866 using a file that maps =E2=80=9Ccpb=E2=80=9D to n64866 = and then allows apache to do the URL rewrite with a rewrite rule.
In apache/sites-enabled/default-s= sl
RewriteMap glidmap txt:/etc/apache2/vivo_glid_map.txt
#rewrite engine changes
&n= bsp;RewriteEngine On
&n= bsp;RewriteMap glidmap txt:/etc/apache2/vivo_glid= _map.txt
&n= bsp;RewriteCond ${glidmap:$1|Unknown} !Unknown
&n= bsp;RewriteRule ^/individual/(.*)$ /individual/${glidmap:$1|$1} [R,L= ]
&n= bsp;RewriteCond ${glidmap:$1|Unknown} !Unknown
&n= bsp;RewriteRule ^/display/(.*)$ /individual/${glidmap:$1|$1} [R,L]= span>
=E2=80=9Cglidmap=E2=80=9D is a fi= le in /etc/apache2/vivo_glid_map.txt
format =3D cpb n12345
tab delimited file with 2 columns= =E2=80=9Clabel=E2=80=9D and =E2=80=9Cvivo N number from URI=E2=80=9D
We have a nightly job that looks = through vivo and parses out peoples email address (IE, cpb@ufl.edu) and then= the N number (n12345) from the profile URI and then WRITES that to the map= file in /etc/apache.
Mostly working on dChecker softwa= re that runs a set of SPARQL queries every day on a cron job, which not onl= y finds malformed data but makes it easier to track down the causes of some= of these data errors
Ran a new people ingest process t= hat created a 52Mb RDF file of additions -- this new process works with peo= ple and contact information from Peoplesoft to decide what has changed and = process the additions and retractions in VIVO; with 1.6 this can become mor= e automated. Represents a couple months of work.
Memorial (John, Max) -- have been= wondering whether it=E2=80=99s possible to have a standardized format for = the VIVO URIs. Florida has a mapping implemented via Apache URL rewri= te rule and a big matching list that allows dynamically connecting from the= institution=E2=80=99s GatorId to the native VIVO URI. Also playing with th= e SPARQL query builder and experimenting with SPARQL constructs. Also= looking at experimenting with a Drupal front end based on what Miles Worth= ington has done in the past (e.g., http://impact.cals.cornell.edu<= /a>)
NYU (Yin) -- sympathetic to the B= oulder area for its water issues =E2=80=A6 (Alex) Thankfully the data cente= r stayed up -- more the employees and general public affected.
= li>UCSF (Eric) -- OpenSocial gadgets= can read but not yet produce linked open data, but are working on solving = that -- extended the VIVO ontology with an ORNG space (http://www.orng.info<= /a>). Now when gadgets save data it will be exposed as linked open data. &n= bsp;A lot of websites are grabbing data out of UCSF Profiles and see things= like news, slideshare and youtube videos, etc. and haven=E2=80=99t been ab= le to share that data. Each gadget would have a mini-definition of an= OWL file that can formally extend the data model -- not sure how brave we = want people to be in extending the ontology, but it should at least be less= intimidating to play around with making data that can also be available.= span>
Also, trying to use the disambigu= ation service built into Profiles that could be used to seed a registry of = URIs for authors from PubMed -- this is the central service that could be c= onnected to a VIVO through its API. Each week when connect to the ser= vice to find authors for UCSF, they could also indicate the local UCSF Prof= iles URI for authors who are identified, aligned with the Pubmed Id. This w= ould enable other people who connect to the service to identify a URI for a= uthors they may not be able to identify since the authors work at a differe= nt institution from their own. Titus Schleyer has connected this service to= Digital Vita at the University of Pittsburgh.
Eric will be working with Griffin= Weber to see if this can be added to the service where it=E2=80=99s hosted= at Harvard
Will bring this up on the tools g= roup -- will have a very low barrier to entry. Chris would love to have Eri= c present the disambiguation service, even before it can be made to serve a= s a URI registry.
Virginia Tech (Curtis) -- in the = process of trying to set up hardware through central IT
Weill Cornell (Paul and Eliza) -- still working on the same th= ings as last week
Would one server with 2GB RAM be = enough for this test installation? Should be enough for a test instance usi= ng a small dataset.
Is MySQL 5.1 required, or could M= ySQL 5.0.95 also work? We can=E2=80=99t recall any changes with 5.1 t= hat would be different for Jena=E2=80=99s SDB library (that VIVO uses) vs. = 5.0.95
Same for Java: 6? And Tomcat: 6 o= r 7? We recommend starting with Java 7 since Java 6 is no longer supp= orted.
Jon shared his experience of purc= hasing small Linux box with 4GB/1TB drive for $375 -- why constrain VIVO op= erating environment to such minimal RAM?
Date: Every Thursday, no end date
Time: 1:00 pm, Eastern Daylight Time = (New York, GMT-04:00)
Meeting Number: 641 825 891
To join the online meeting
Go to https://cornell.webex.com/cornell/e.php?AT=3DWMI&EventID=3D1670963= 22&RT=3DMiM2
If requested, enter your name and ema= il address.
Click "Join".
To view in other time zones or langua= ges, please click the link: https://cornell.webex.com/cornell/globalcallin.php?serviceType=3DMC&a= mp;ED=3D167096322&tollFree=3D1
If those links don't work, please vis= it the Cornell meeting page and l= ook for a VIVO meeting.
To join the audio conference only
To receive a call back, provide your = phone number when you join the meeting, or call the number below and enter = the access code.
Call-in toll-free number (US/Canada):= 1-855-244-8681
Call-in toll number (US/Canada): 1-65= 0-479-3207
Global call-in numbers: &= nbsp;https://cornell.webex.com/cornellun= iversity/globalcallin.php?serviceType=3DMC&ED=3D161711167&tollFree= =3D1
Toll-free dialing restrictions: = http:= //www.webex.com/pdf/tollfree_restrictions.pdf
Access code:645 873 290