(Trans)Planting Digital Vita: Document generation for VIVO

8/4/2019 (Trans)Planting Digital Vita: Document generation for VIVO

http://slidepdf.com/reader/full/transplanting-digital-vita-document-generation-for-vivo 1/28

(Trans)planting

Digital Vita:

Document

generation for

VIVO Titus Schleyer, DMD, PhD1, Stella Mitchell,MS2, Shiyi Shen, MS1, William Shirey, MS1,Jon Corson-Rikert2, Brian Lowe2, MichaelBecich, MD, PhD1, Linda Schmandt, MS1

1University of Pittsburgh2Cornell University

L i c e n s e d i m a g e ( h t t p : / / w w w . 1 2 3 r f . c o m / ) 2 0 1 1

http://www.123rf.com/
























DV Docs for VIVOTitus Schleyer et al. 2 of 27

The one-click pony

http://vivo-dev.dlib.indiana.edu/display/person25557






http://di.dental.pitt.edu/orc/




Document generation in DV

• CV information maintained in My

Information

• My Documents

– create, edit and (delete) documents (CV, onlineprofile and NIH biosketches)

– editing limited to including/excluding My Info items

– Lego principle

Licensed image (http://www.123rf.com/) 2011






[Backup slides for online demo of DV]






















Project goal and deliverables

• Goal: transplant DV document generation

functions to VIVO

• Deliverables

– Java Application Programming Interface (API)(VIVO RDF/XML -> RTF/PDF)

– Web service version of the API for non-Javaenvironments

– Web application for generating CVs and NIHbiosketches

– full documentation




Map data fields: Biography, Education andPosition

exact match

similar

no match









similar

no match

exact match




Mapping data fields: Lessons

• DV and VIVO describe the same/similar entities, but in different ways.

• Data model mapping challenges

–

field level mapping (e.g. semantics, fieldcharacteristics)

– structural mapping (e.g. classes and their relationships)

–

no corresponding mappings (e.g. the concept“present”)




Technical approach

• profile obtained from VIVO using the LinkedData Rich Export in rdf/xml format

• rdf/xml converted to xml using XSPARQL

(xsparql.deri.org) (see XSPARQL example)• Apache Formatting Objects Processor (FOP)

converts xml to a pdf or rtf document

http://vivo-dev.dlib.indiana.edu/individual/person25557/person25557.rdf?include=all

http://localhost/var/www/apps/conversion/tmp/scratch_4/25557.xml

http://xsparql.deri.org/

http://localhost/var/www/apps/conversion/tmp/scratch_4/vivo2dv.xs

http://xmlgraphics.apache.org/fop/

http://xmlgraphics.apache.org/fop/

http://localhost/var/www/apps/conversion/tmp/scratch_4/vivo2dv.xs


http://localhost/var/www/apps/conversion/tmp/scratch_4/25557.xml

http://vivo-dev.dlib.indiana.edu/individual/person25557/person25557.rdf?include=all




Example conversions

A person’s VIVO profile in rdf/xml

<rdf:Description rdf:about="http://vivo.iu.edu/individual/person25557">

<j.5:firstName>Katy</j.5:firstName>

<j.5:lastName>Borner</j.5:lastName>

<j.6:workEmail>katy(AT)indiana(DOT)edu</j.6:workEmail>

...

</rdf:Description>

<DocumentIntermediateFormat>

<person>

<familyName>Borner</familyName>

<givenName>Katy</givenName>

...

</person><personsEmailContacts>

<emailAddress>katy(AT)indiana(DOT)edu</emailAddress>

<use>business</use>

</personsEmailContacts>

...

</DocumentIntermediateFormat>

is converted to the XML format used by Digital

Vita’s document generation engine.







Technical approach

• Evaluated several approaches to transform

RDF/XML to XML – custom Java

– XSLT

•

settled on XSPARQL – easing the transformation with an innovative

language based on a combination of XQueryand SPARQL

–

well-thought out, but still early






Jan Feb Mar Apr May Jun Jul Aug

Map data fields between VIVO and DV

Develop data extraction methods

Develop doc. gen. APIImplement Web application

User testing

Document work products and release

Present results

Where we should be today




Jan Feb Mar Apr May Jun Jul Aug

Map data fields between VIVO and DV

Develop data extraction methods

Develop doc. gen. APIImplement Web application

User testing

Document work products and release

Present results

Where we are today




Next Steps

•

application interface for managing CVs andbiosketches

– customize existing content

• e.g., publications

– enter biosketch-specific information• e.g, personal statement

– configure options

• sorting

• citation style

– persist as named profile




Document configuration model in VIVO




Discussion and outlook

•

successful (for now, partial) transfer offunctionality from DV to VIVO

• mapping data models required significant

effort

• The way forward: An “App Store” for research networking?




Please visit us at:

http://di.dental.pitt.edu/orc

Twitter Facebook /titusschleyer

Scribd }

Thank You for Your Attention!

Questions, comments?

(Yeah!)

Thanks to:

• NCRR award 1 U54 RR023506-01

• VIVO Collaborative Grant Program throughNCRR award U24RR029822

• Dr. Axel Polleres, Nuno Lopes and others at

DERI

P u b l i c d o m a i n i m

a g e ( h t t p : / / k a r e n s w h i m s y . c o m

/ t r e e - c l i p a r t . s h t m ) 2 0 1 1



DV Docs for VIVOTitus Schleyer et al.

http://scr.bi/pGX6tk

Date post:	07-Apr-2018
Category:	Documents
Upload:	titus-schleyer
View:	219 times
Download:	0 times