...
Notable implementation and development list issues
Adding link to institutional repository
- (Giuseppe)
vivo:realizedRole and vivo:contributingRole
- (Boliang) I created an organization object and want to add a contributor to it. There is an error showing "There are no entries in the system from which to select." It also happens to an event object when adding a participant. The contributor property in organization is vivo:contributingRole and the participant property is vivo:realizedRole. We are using vivo 1.5. I also deployed another vivo 1.6 in my local for testing. But I didn't found these two properties in vivo 1.6. Are they removed in vivo 1.6?
Proxy editing
- (Paul) Would someone please confirm for me that there is no existing way to allow a departmental administrator or admin assistant to function as a proxy editor with VIVO? I saw this wiki article but not much else: https://wiki.duraspace.org/display/VIVO/Delegate+someone+to+edit
- (Jim) Yes and no. Yes, any individual can designate another user to be a proxy editor for them, or any admin can manage the designation. An individual can do this by logging in, going to the drop-down under their name in the upper right, choosing "My Account" and "Who can edit my profile". An admin can do this by going to the "Site Admin" page and choosing "Manage Profile Editing". No, there is no way to establish a rule by which you say, "this person will function as proxy editor for all members of this department". Proxies must be established explicitly, rather than implicitly. Proxy editing by rule is still a wish-list item.
Jira server DuraSpace JIRA key VIVO-236
VIVO usage data
- (Bart) I've been asked by our School of Medicine Dean if there is any usage data for institutions that have a VIVO instance up and running. Please let me know if there is any data that you can share. She didn't ask for anything specific, anything quantitative or qualitative would be helpful. This information would be shared with SOM administration as well as other departments at the University of Virginia.
Jena source of slow MySQL queries for publications
- (Mark) Folks - it would be great if anyone could replicate some behaviour we are seeing with respect to the MySQL queries generated by Jena for publications. We have been doing some profiling and are seeing some very suboptimal MySQL queries being generated. The situation is that each query seems to consist of pretty much every triple related to every publication, a theory somewhat borne out by the fact that the exact same query is issued every time for any publication you request. It is almost as if there is just a single standard query being done for all pubs, and then from that result set a temporary in memory graph is created, queried and then discarded ...
- (BrianL) Have you done any local customization of the SPARQL queries used to render publication pages, such as list views? My first guess would be that there's a SPARQL query somewhere with the triple patterns written in an order that leads to inefficient MySQL. VIVO should be passing all of the mission-critical SPARQL queries directly to SDB to optimize as it sees fit, but it seems that SDB doesn't always quite generate the SQL joins you might expect. It's also possible that you're seeing the result of a query that's being routed through more complex layers of Jena models, which usually forces each triple pattern to be evaluated one at a time and joined in Java. In these cases the order in which the query is written can have an enormous impact on performance (though sometimes these queries can be faster than the ones with complex SQL joins).
| Panel | ||
|---|---|---|
| ||
As an example, let's suppose the predicate in question is vivo:linkedAuthor. If you see a query like the following, where ?publication gets prebound to a particular publication URI, WHERE { } then rewriting it as WHERE { } so that the specific publication URI comes first might fix the problem. |
- (Mark --) You were spot on - we had a misplaced union in a listview.
...
- List of sessions and poster posted here (PDF)
- Register before July 19 for best rate and conference hotel availability
- https://www.eiseverywhere.com/ehome/vivo2013/register/
- July 20th – August 13th - $550
- Onsite - $600
- Conference hotel is Hilton St. Louis at the Ballpark Hotel
- Click here to book your hotel room reservation.
- Wednesday night baseball game (Cardinals vs Pirates) and cold beer!
...
Updates
- Brown
- Colorado
- Cornell
- Duke
- Johns Hopkins
- Memorial
- RPI
- Scripps
- Stony Brook
- Texas A&M
- UCSF
- Virginia Tech
- Weill CornellUCSF
Call-in Information
Date: Every Thursday, no end date
...