Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import Insight Journal #529

Open
3 tasks
hubsmoke opened this issue Sep 26, 2024 · 1 comment
Open
3 tasks

Import Insight Journal #529

hubsmoke opened this issue Sep 26, 2024 · 1 comment
Assignees

Comments

@hubsmoke
Copy link
Member

hubsmoke commented Sep 26, 2024

About: https://insight-journal.org/
Data: https://github.com/InsightSoftwareConsortium/InsightJournal

  • Import ~1000 research objects
  • Make each have dpid + a "version of record" DOI on CrossRef ($1 each)
  • Create an ARC with these in there
@m0ar
Copy link
Contributor

m0ar commented Oct 9, 2024

Some details from discussions with @hubsmoke:

  • We will do this as actual research objects, but it will not be possible for the authors to claim them because it's made with a different DID. This is OK.

  • We could potentially have imported them as "soft" nodes, i.e. public nodes that doesn't have an actual research object. This way, original authors could claim them. We choose not to do this, because:

    • engineering is more complex, both on app and backend side
    • new access type to support going forward, in an already complex flow
    • it's a good scalability test for the protocol(s)
  • Regarding key management, these were the alternatives:

    1. Create all of them with a known, new key (1 key controlling n research objects)
    2. Create each with a known, individual new key (n keys controlling n research objects)
    3. Create all with a key we throw away ("tombstone" imports, no updates possible)

    We are going with 1, keeping the option open for Insight Journal to manage the objects themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants