Publications
Search

Publications :: Search

Show author

On this page you see the details of the selected author.

    Author information
    First name: Paul Logasa Bogen
    Last name: II
    DBLP: 95/3883
    Rating: (not rated yet)
    Bookmark:

    Below you find the publications which have been written by this author.

    Show item 1 to 5 of 5  
    Select a publication
    Show Title Venue Rating Date
    Paul Logasa Bogen II, Joshua Johnston, Unmil Karadkar, Richard Furuta, Frank M. Shipman III.
    Application of kalman filters to identify unexpected change in blogs.
    ACM/IEEE Joint Conference on Digital Libraries, JCDL 2008, Pittsburgh, PA, USA, June 16-20, 2008 2008 (0) 2008
    Paul Logasa Bogen II, Luis Francisco-Revilla, Richard Furuta, Takeisha Hubbard, Unmil Karadkar, Frank M. Shipman III.
    Longitudinal study of changes in blogs.
    ACM/IEEE Joint Conference on Digital Libraries, JCDL 2007, Vancouver, BC, Canada, June 18-23, 2007, Proceedings 2007 (0) 2007
    Sarah Davis, Paul Logasa Bogen II, Lauren Cifuentes, Luis Francisco-Revilla, Richard Furuta, Takeisha Hubbard, Unmil Karadkar, Daniel Pogue, Frank M. Shipman III.
    Template-based authoring of educational artifacts.
    ACM/IEEE Joint Conference on Digital Libraries, JCDL 2006, Chapel Hill, NC, USA, June 11-15, 2006, Proceedings 2006 (0) 2006
    Pratik Dave, Luis Francisco-Revilla, Unmil Karadkar, Richard Furuta, Frank M. Shipman III, Paul Logasa Bogen II.
    Incorporating Physical and Digital Artifacts into Growing Personal Collections.
    Research and Advanced Technology for Digital Libraries, 8th European Conference, ECDL 2004, Bath, UK, September 12-17, 2004, Proceedings 2004 (0) 2004
    Pratik Dave, Paul Logasa Bogen II, Unmil Karadkar, Luis Francisco-Revilla, Richard Furuta, Frank M. Shipman III.
    Dynamically growing hypertext collections.
    HYPERTEXT 2004, Proceedings of the 15th ACM Conference on Hypertext and Hypermedia, August 9-13, 2004, Santa Cruz, California, USA 2004 (0) 2004

    Your query returned 5 matches in the database.