Website Search Results

    Page 1 of 12 website results

    1. Adventures in metadata hygiene: using Open Refine, XSLT, and Excel to dedup and reconcile name and s

      XSLT template that find and replaces old values with cleaned ones.  

    2. Duke Collaboratory for Classics Computing (DC3) - Page 2 of 20 - a collection of parts flying in loo

      XSLT 3.0 looks to have no OSS implementation at all.

    3. There's a new whale in town - Duke Collaboratory for Classics Computing (DC3)

      XSLT 3.0 looks to have no OSS implementation at all.

    4. Bitstreams: The Digital Collections Blog - Page 28 of 36 - Notes from the Duke University Libraries

      XSLT template that find and replaces old values with cleaned ones.  

    5. Revitalizing DSpace at Duke - Bitstreams: The Digital Collections Blog

      From http://demo.dspace.org/xmlui/ The UI framework itself is outdated (driven via XSLT 1.0 through Cocoon XML pipelines ), which makes (...)

    6. Open Scholarship in the Humanities: Ann Chapman Price - Duke University Libraries Blogs

      Not knowing XSLT, I chose to create a visualization of my edition by using an open-source software called EVT (Edition Visualization (...)

    7. New Angles & Avenues for Bitstreams - Bitstreams: The Digital Collections Blog

      Seven years ago, we were writing custom XSLT to create and then consume our own RSS feeds in Cascade Server CMS.

    8. Duke Collaboratory for Classics Computing (DC3) - Page 17 of 20 - a collection of parts flying in lo

      In testing this across the entire corpus, I started to notice that certain characters were causing problems – while Leiden+ uses Java’s Unicode (...)

    9. Getting to the Finish Line: Wrapping Up Digital Collections Projects - Bitstreams: The Digital Colle

      UCLA’s Library recently published a “Library Special Collections Digital Project Toolkit” that includes an “Assessment and Evaluation” section (...)

    10. Perfectly normal - Duke Collaboratory for Classics Computing (DC3)

      In testing this across the entire corpus, I started to notice that certain characters were causing problems – while Leiden+ uses Java’s Unicode (...)

    More Search Options