[DDI-SRG] TC: Minutes postes
Wendy Thomas
wlt at umn.edu
Mon Mar 18 10:52:50 EDT 2019
Note that the only place a DDI URN is used is in the creation and
publication of the Controlled Vocabulary. The CodeValueType supports any
type of URN (actually it's a type xs:string) because we wanted you to be
able to reference any format of controlled vocabulary whether it could be
processed or not. You could, in fact, reference a PDF. -- Wendy
On Mon, Mar 18, 2019 at 6:47 AM Wackerow, Joachim <
Joachim.Wackerow at gesis.org> wrote:
> It is usually not a good idea to semantic information (date, internal log
> combination) into an identifier like the DDI URN.
>
>
>
> It sounds like an approach like UserID in 3.2 could be an option. This is
> an id and version from a different system as the DDI URNs. It can be
> understood as a parallel id to the DDI URN.
>
> See:
> http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/elements/UserID.html
>
>
>
> Achim
>
>
>
>
>
> *From:* Taina Jääskeläinen (TAU) [mailto:taina.jaaskelainen at tuni.fi]
> *Sent:* Montag, 18. März 2019 09:02
> *To:* Wendy Thomas
> *Cc:* Sanda Ionescu; Wackerow, Joachim; Hopt, Oliver; DDI Structural
> Reform Working Group.
> *Subject:* RE: TC: Minutes postes
>
>
>
> Thanks for the responses, Wendy.
>
> It would be helpful for users if DDI Alliance would not need a different
> kind of version number system from the way DDI CVG has envisioned the
> versioning (two-digit for source language CV, three-digit for the target
> languages where first two digits are the source version number). The
> separate versioning for languages was based on explicitly expressed user
> needs. For example, a language version of a CV might be used in
> self-report software where depositors of data can describe their studies
> for the data archive.
>
>
>
> So I wonder if the whole package versioning be managed with some kind of
> date + internal log combination you mentioned? Oliver?
>
> The change log information for each language can be taken from the
> elements Version changes and Version notes (if any) for published CVs, and
> new added or withdrawn languages from publish or withdraw functions?
>
> BTW, would it be possible for users to glean changes only in one or two
> language versions from the whole package, based on the language code?
>
>
>
> But there may be user needs or technical issues involved that I cannot
> envision…. And cannot say how any APIs work.
>
>
>
> The urn recorded for DDI vocabularies in the CESSDA tool in Canonical URIs
> and Canonical URIs of the version is naturally the DDI urn. So for citation
> in DDI Alliance website, Canonical URIs need no changes but URL would be to
> DDI Alliance website.
>
>
>
> All the best, Taina
>
>
>
> ---
>
> Taina Jääskeläinen
>
> FSD Finnish Social Science Data Archive
>
> Tampere University, FINLAND
>
> e-mail: taina.jaaskelainen at tuni.fi | tel: +358 40 190 1444
> http://www.fsd.uta.fi
>
>
>
> *From:* Wendy Thomas <wlt at umn.edu>
> *Sent:* 15. maaliskuuta 2019 16:25
> *To:* Taina Jääskeläinen (TAU) <taina.jaaskelainen at tuni.fi>
> *Cc:* Sanda Ionescu <sandai at umich.edu>; Wackerow, Joachim <
> Joachim.Wackerow at gesis.org>; oliver.hopt at gesis.org; DDI Structural Reform
> Working Group. <ddi-srg at icpsr.umich.edu>
> *Subject:* Re: TC: Minutes postes
>
>
>
> Taina,
>
>
>
> Basically we will publish a SKOS instance that contains all languages and
> therefore have a single version number. How the version number is defined
> can be up to us. So yes we could say that the major version doesn't change
> unless the terms change or there is a significant correction in the
> intellectual content of a definition. The reference could be to the major
> version and the user would get the most recent sub-version of that. Some
> people do sub-versions simply using dates and internal change log with a
> date, change, and reason for change. For example: 2019-03-15, Term X
> definition (en) Aggregaetion changed to Aggregation, Corrected misspelling
> OR 2019-03-15 Added labels and definitions in German (de), added
> translation option. In short, it is up to us to determine the versioning
> rules and make them clear to users. In making a decision on this the
> primary issue should be user needs. What changes actually have an impact on
> the user and the value of stability in the version numbers.
>
>
>
> The primary concerns of the call with TC was to make sure we had
> identified all the technical things that needed to be decided and
> completed. In particular to identify interaction points with the CESSDA
> tool, the production pipeline, CV/TC, and ICPSR/Web page. I will add a line
> to the minutes that the UNESCO link was simply and example
>
>
>
> If I understood Oliver correctly we could get a merged language output in
> SKOS from the CESSDA tool. If not it is simply an additional step in the
> production pipeline to create a merged version from the individual language
> versions prior to transformation to other formats and publication. Oliver
> should have this in his workflow.
>
>
>
> I will add a note in the minutes about the UNESCO link being an example of
> presenting multiple languages.
>
>
>
> Regarding citation, yes, the DDI publication will provide DDI URN and URL
> (probably to the SKOS version as the source)...that can be decided. It
> should line up with the target of the resolved URN. Actually, since we have
> multiple formats we will need to consider just WHAT the URN is landing on.
> This may result in reorganization of the web content. I will note this in
> the minutes.
>
>
>
> Thanks for these clarifications.
>
> Wendy
>
>
>
> On Fri, Mar 15, 2019 at 6:13 AM Taina Jääskeläinen (TAU) <
> taina.jaaskelainen at tuni.fi> wrote:
>
> Hi Wendy,
>
> Reading the minutes, a couple of clarifications, though please note that I
> may have misunderstood.
>
>
>
> Versioning:
>
> - If I understood correctly, DDI Alliance will want to version
> the whole package with all language versions? If there is change in any
> language versions, the whole package version changes. I can see this is
> useful if, for example, the CV is used as a multilingual filter in a search
> interface.
>
> - The CESSDA tool versions each language separately, though the
> translations have a three-digit version number linked to the source as the
> first two digits are the source version number (i.e. 2.0.2 means the second
> TL version of the source version 2.0). This is useful for users who are
> using the CV in their metadata. They are only interested in when and what
> has been changed in their language version to see what needs to be changed
> in their legacy metadata and in their systems where the CV is implemented.
>
> - The issue maybe to discuss is how to produce the whole package
> versioning, in the merged SKOS of the CESSDA tool, or in the DDI
> publication pipeline? But this is technical, so out of my expertise.
>
>
>
> The link to the Unesco vocabularies was just an example of the one typical
> html display of multilingual vocabularies. Based on open source publication
> platform skosmos. It displays the whole language version on the left and
> term-specific display on the right. In term-specific display all language
> versions of a specific term are displayed. What is lacking, I think, is the
> possibility to click on any language term on the right and change language
> that way.
>
>
>
> Regarding the citation, the citation in the CESSDA tool has both URN and
> URL. Did we conclude that in CESSDA tool the citation URL is to that tool,
> and in DDI Alliance website the URL in citation is to the DDI Alliance
> webpage? That would need to be taken into account in the DDI publication
> pipeline.
>
>
>
> All the best, Taina
>
>
>
> ---
>
> Taina Jääskeläinen
>
> FSD Finnish Social Science Data Archive
>
> Tampere University, FINLAND
>
> e-mail: taina.jaaskelainen at tuni.fi | tel: +358 40 190 1444
> http://www.fsd.uta.fi
>
>
>
> *From:* Wendy Thomas <wlt at umn.edu>
> *Sent:* 14. maaliskuuta 2019 18:55
> *To:* Taina Jääskeläinen (TAU) <taina.jaaskelainen at tuni.fi>; Sanda
> Ionescu <sandai at umich.edu>
> *Subject:* Fwd: TC: Minutes postes
>
>
>
>
>
> ---------- Forwarded message ---------
> From: *Wendy Thomas* <wlt at umn.edu>
> Date: Thu, Mar 14, 2019 at 11:39 AM
> Subject: TC: Minutes postes
> To: DDI Structural Reform Working Group. <ddi-srg at icpsr.umich.edu>
>
>
>
> Today's meeting focused on CVs and the new production pipelines for
> publication. Taina and Sanda joined the meeting. Minutes are at
>
>
> https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/491551/TC+Meeting+Minutes
>
>
>
> Action items coming out of this meeting:
>
> 1. TC needs to survey DDI users and determine who is using Genericode
> structures currently and whether this structure should be persisted given
> other options that will be made available for CVs
> 2. CVG needs to provide summary of desired functionality for the CV
> web pages so that priorities can be determined for changes
> 3. TC and CVG need to write up new production process from creation of
> content using CESSDA tool and export of SKOS file, through production and
> review, to publication and announcement. This must be completed for
> presentation at the Scientific Board meeting.
>
> Many thanks to Taina and Sanda for joining the TC meeting!
>
>
> --
>
> Wendy L. Thomas Phone: +1 612.624.4389
>
> Data Access Core Director Fax: +1 612.626.8375
>
> Minnesota Population Center Email: wlt at umn.edu
>
> University of Minnesota
>
> 50 Willey Hall
>
> 225 19th Avenue South
>
> Minneapolis, MN 55455
>
>
>
> --
>
> Wendy L. Thomas Phone: +1 612.624.4389
>
> Data Access Core Director Fax: +1 612.626.8375
>
> Minnesota Population Center Email: wlt at umn.edu
>
> University of Minnesota
>
> 50 Willey Hall
>
> 225 19th Avenue South
>
> Minneapolis, MN 55455
>
>
>
> --
>
> Wendy L. Thomas Phone: +1 612.624.4389
>
> Data Access Core Director Fax: +1 612.626.8375
>
> Minnesota Population Center Email: wlt at umn.edu
>
> University of Minnesota
>
> 50 Willey Hall
>
> 225 19th Avenue South
>
> Minneapolis, MN 55455
>
--
Wendy L. Thomas Phone: +1 612.624.4389
Data Access Core Director Fax: +1 612.626.8375
Minnesota Population Center Email: wlt at umn.edu
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20190318/09151545/attachment-0001.html
More information about the DDI-SRG
mailing list