Show simple item record

hal.structure.identifierLuxembourg Centre For Systems Biomedicine [LCSB]
dc.contributor.authorAlper, Pinar
ORCID: 0000-0002-2224-0780
hal.structure.identifierLaboratoire d'analyse et modélisation de systèmes pour l'aide à la décision [LAMSADE]
dc.contributor.authorBelhajjame, Khalid
hal.structure.identifier
dc.contributor.authorCurcin, Vasa
ORCID: 0000-0002-8308-2886
hal.structure.identifierSchool of Computer Science [Manchester]
dc.contributor.authorGoble, Carole
ORCID: 0000-0003-1219-2137
dc.date.accessioned2023-02-07T16:01:01Z
dc.date.available2023-02-07T16:01:01Z
dc.date.issued2018
dc.identifier.issn2227-9709
dc.identifier.urihttps://basepub.dauphine.psl.eu/handle/123456789/23987
dc.language.isoenen
dc.subjectWorkflowen
dc.subjectProvenanceen
dc.subjectDomain-specific annotationen
dc.subject.ddc003en
dc.titleLabelFlow Framework for Annotating Workflow Provenanceen
dc.typeArticle accepté pour publication ou publié
dc.description.abstractenScientists routinely analyse and share data for others to use. Successful data (re)use relies on having metadata describing the context of analysis of data. In many disciplines the creation of contextual metadata is referred to as reporting. One method of implementing analyses is with workflows. A stand-out feature of workflows is their ability to record provenance from executions. Provenance is useful when analyses are executed with changing parameters (changing contexts) and results need to be traced to respective parameters. In this paper we investigate whether provenance can be exploited to support reporting. Specifically; we outline a case-study based on a real-world workflow and set of reporting queries. We observe that provenance, as collected from workflow executions, is of limited use for reporting, as it supports queries partially. We identify that this is due to the generic nature of provenance, its lack of domain-specific contextual metadata. We observe that the required information is available in implicit form, embedded in data. We describe LabelFlow, a framework comprised of four Labelling Operators for decorating provenance with domain-specific Labels. LabelFlow can be instantiated for a domain by plugging it with domain-specific metadata extractors. We provide a tool that takes as input a workflow, and produces as output a Labelling Pipeline for that workflow, comprised of Labelling Operators. We revisit the case-study and show how Labels provide a more complete implementation of reporting queries.en
dc.relation.isversionofjnlnameInformatics
dc.relation.isversionofjnlvol5en
dc.relation.isversionofjnlissue1en
dc.relation.isversionofjnldate2018-02
dc.relation.isversionofdoi10.3390/informatics5010011en
dc.relation.isversionofjnlpublisherMDPIen
dc.subject.ddclabelRecherche opérationnelleen
dc.relation.forthcomingnonen
dc.description.ssrncandidatenon
dc.description.halcandidatenonen
dc.description.readershiprechercheen
dc.description.audienceInternationalen
dc.relation.Isversionofjnlpeerreviewedouien
dc.date.updated2023-02-07T14:24:49Z
hal.export.arxivnonen
hal.export.pmcnonen
hal.hide.repecnonen
hal.hide.oainonen
hal.author.functionaut
hal.author.functionaut
hal.author.functionaut
hal.author.functionaut


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record