Uploaded image for project: 'SIdora'
  1. SIdora
  2. SID-592

As an SCBI-CT user, I want the ingest process to use the parent object IDs from the manifest as the unique identifier falling back to names for lookups

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Fixed
    • Icon: Major Major
    • 0.6.0
    • 0.4.3
    • Services
    • None

      As an SCBI-CT user, I want the ingest process to use the parent object IDs (ProjectId, SubProjectId, DeploymentId) as the unique identifier for the look ups falling back to using names. Currently, the SCBI-CT routes use the parent hierarchy's names to look up the to see if the object already exists in the repository instead of using the ID. There are few constraints that are limiting us from switching from names to IDs:

      PlotId does not exist in the deployment manifest model yet so it must continue to use name.

            BirkhimerJ Birkhimer, Jason
            DavisDa Davis, Daniel [X] (Inactive)
            Archiver:
            ThompsonK Thompson, Keri

              Created:
              Updated:
              Resolved:
              Archived: