Skip to main content

Notice

We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities: https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/

Forum Replies Created

Page 1 of 2
  • Author
    Replies
  • in reply to: #129209

    Dear Anita,
    Thanks for the info and congrats on the award. Please get back to us
    at your convenience.
    Cheers, m.
    On Wed, Sep 7, 2022 at 11:44 AM ***@***.*** via Persistent
    Identification of Instruments WG

  • in reply to: #129239

    Hi Jonathan,
    overall looks good to me, few comment on this statement: “There is a
    mapping with DataCite schema (to assign a DOI to your instrument) and
    ePIC This way, an instrument can be assigned with a DOI or a Handle.”
    * ePIC and DataCite are two *implementations* of PIDINST schema,
    DataCite requires a schema mapping and ePIC is a full PIDINST schema
    implementation
    * DataCite DOIs are Handles, too, and I believe ePIC IDs can be
    resolved via https://doi.org.
    Cheers, m.
    On Fri, Jun 3, 2022 at 4:26 PM Jonathan Schaeffer via Persistent
    Identification of Instruments WG

  • in reply to: #129256

    Hi Jonathan,
    In addition to the white paper, this [1] is a relevant article, which
    is, however, a bit older, but still provides context. The recent
    schema publication [2] is surely also of interest. The Github repo [3]
    may also be useful. Finally, in the Drive folder of past plenaries [4]
    there is also presentation material that may be useful.
    Cheers, m.
    [1] https://doi.org/10.5334/dsj-2020-018
    [2] https://doi.org/10.15497/RDA00070
    [3] https://github.com/rdawg-pidinst/
    [4] https://drive.google.com/drive/folders/0B2Jvjtf4IpFNZURWcC02LWpWWk0?reso
    On Wed, May 4, 2022 at 5:19 PM Jonathan Schaeffer via Persistent
    Identification of Instruments WG

  • in reply to: #129284

    Dear all,
    Agreed with Rolf, thanks for the invite Baptiste. Sven, please go
    ahead with your proposal!
    Cheers, m.
    On Tue, Feb 15, 2022 at 9:22 AM rolf.krahl via Persistent
    Identification of Instruments WG

  • in reply to: #129698

    Very useful, indeed. Thanks for pointing it out, Simon. FYI, if you
    wonder where the URI of the term is, as I did, it’s at the top in the
    right panel, below the term name there is an IDURI switch. This
    could be more prominent but otherwise the interface is a big
    improvement for QUDT use.
    m.
    On Mon, Jul 13, 2020 at 8:02 AM mabablue via InteroperAble
    Descriptions of Observable Property Terminology WG (I-ADOPT WG)

  • in reply to: #129799

    Dear Nikola,
    great, looking forward to meeting you on a future call!
    Cheers, m.
    On Wed, May 27, 2020 at 2:07 PM niva via Persistent Identification of

  • in reply to: #129806

    Dear Nikola,
    Thanks for your interest and for reaching out! Your case sounds very
    interesting.
    You have probably already seen this, we keep the use case descriptions here:
    https://github.com/rdawg-pidinst/use-cases
    In principle you can grab an existing one as a template. Feel free to
    post a PR and we will review/integrate it.
    Subsequently, we can see whether the current schema meets your
    requirements. For this, you would ideally join a future call, which
    are on first Wed every month at 2 pm UTC. I will send a reminder about
    the next call next week.
    Hope this helps.
    Cheers, m.
    On Wed, May 27, 2020 at 1:26 PM niva via Persistent Identification of

  • in reply to: #130539

    All,
    since some key people are unavailable tomorrow, let’s move the call to
    next week Wed at 10 am CEST (8 am UTC).
    Hope this works.
    Cheers, m.
    On Mon, Jun 3, 2019 at 11:33 AM rolf.krahl

  • in reply to: #130563

    Hi Rolf,
    I think it is a good idea. Personally, I am a bit unclear on what days
    I can be in Helsinki so there is a bit of uncertainty regarding my
    presence but that shouldn’t hinder this. More importantly, we would
    probably need to have this side meeting right after the plenary, in
    the afternoon of the last day. I am not sure to what extent we can
    control this. I worry a bit that it will be difficult to get enough
    people to this event if it happens to be a day or two before the
    plenary.
    Cheers, m.
    On Thu, May 16, 2019 at 8:37 AM rolf.krahl

  • in reply to: #130637

    Dear Ted,
    Thanks very much for the interesting and useful analysis. We will take
    this on in discussions and future work. Please consider joining a
    future group call (next week Wed 2 pm UTC; will send out a reminder).
    Cheers, m.

  • in reply to: #130700

    Thanks, Rolf, for implementing the decisions we made in the call.
    There are still some open issues against which some of you are tagged.
    Please inform us if the recent changes address your concerns. Thanks,
    all.
    Cheers, m.
    On Wed, Mar 6, 2019 at 2:11 PM rolf.krahl

  • in reply to: #130897

    Rolf, all,
    Apologies, I forgot to update my own calendar entry after our last decision
    to move this call from 6 pm to 4 pm CEST. The information in the call
    announcement was correct. Thanks to your email earlier, we had a speedy
    call but I think still managed to go through the agenda and fix the next
    steps.
    Cheers, m.
    On Wed, Oct 17, 2018 at 4:34 PM rolf.krahl
    wrote:

  • in reply to: #130940

    Bob,
    thanks for this, great analysis and very useful. Many thanks to your
    colleague. I will take a closer look tomorrow. I believe we can build on
    this as it seems a simple and sensible approach.
    Cheers, m.

  • in reply to: #131039

    I obtained feedback from Lesley and she will attend P12. I will clarify the
    joint session idea with her. @Jay, do you confirm that groups involved in
    joint sessions won’t be given a separate group session? I agree with Jacco,
    if Lesley agrees on a joint session with OD2I I suggest prioritize that
    over a separate group session. But I am open to hear other opinions, pros
    and cons. I guess we can submit both and then see what happens / withdraw
    later.
    On Thu, Jun 21, 2018 at 3:26 PM Jay Pearlman
    wrote:

  • in reply to: #131130

    Dear Ana,
    Thanks very much for the use case description. I will read and provide
    comments before the next meeting.
    @All: Those of you who use a definition for instruments, can you write it
    down here [1]? Thanks!
    Cheers, m.
    [1]
    https://docs.google.com/document/d/1AxeYSIA2LahvVprIDRmb0wm7U71lTiQt0n0f

Page 1 of 2