Osoba:
Nicolas, Yann

Profilový obrázek
Emailová adresa
Datum narození
Výzkumné projekty
Organizační jednotky
Název pracovní pozice
Příjmení
Nicolas
Křestní jméno
Yann
Jméno

Filtry

20183
Resetovat filtry

Nastavení

Výsledky vyhledávání

Nyní se zobrazuje 1 - 3 z 3
  • Náhled není k dispozici
    PublikaceOtevřený přístup
    Lightning Talks, June 8
    (2018-06-08) Le Provost, Aline; Greenall, Rurik; Nicolas, Yann; Dennis, Tim; Seige, Leander; Koster, Lukas; Harlow, Christina
    Links Quality for/by Human and Machines - Aline Le Provost, Using Cucumber for Collaboration - Rurik Greenall, SOLR TOTAL. 1000 MARC Fields. 2000 Indexes - Yann Nicolas, Library Carpentry. Software and Data Data Skills for Library Professionals - Tim Dennis, A Lightning Talk on Manuscripts and IIIF - Leander Seige, ELAG Community - Lukas Koster, Christina Harlow
  • Náhled
    PublikaceOtevřený přístup
    Solr Total
    (2018-06-07) Nicolas, Yann
    Lightning Talks (June 8), video recording is available at: http://repozitar.techlib.cz/record/1275
  • Náhled
    PublikaceOtevřený přístup
    From XML to MARC: RDF Behind the Scenes
    (2018) Nicolas, Yann
    We collect heterogeneous metadata packages from various publishers. Although all of them are in XML, they vary a lot in terms of vocabulary, structure, granularity, precision, and accuracy. It is quite a challenge to cope with this jungle and recycling it to meet the needs of the Sudoc, the French academic union cataloguing system. How to integrate and enrich these metadata? How to integrate them in order to process them in a regular way, not through ad hoc processes? How to integrate them with specific or generic controlled vocabularies ? How to enrich them with author identifiers, for instance? RDF looks like the ideal solution for integration and enrichment. Metadata are stored in the Virtuoso RDF database and processed through a workflow steered by the Oracle DB. We will illustrate this generic solution with Oxford UP metadata: ONIX records for printed books and KBART package description for ebooks. So. A relational database as glue and pipeline engine… RDF as internal model… MARC as output …. Quite weird… Was this abstract written by an ELAG-specific random text generator?