"Publication" and "Publication Manifest" under "Choose a Metadata Template Type:"

[aclayton555]

When playing around with the Publication schema, I noted that the HTAN DCA includes both "Publication" and "Publication Manifest" in the dropdown under "Choose a Metadata Template Type"

I seem to get a disconnect if selecting "Publication." "Publication Manifest" seems to work though and appears to be the latest version of the schema.

Is there a way to tidy this up so that contributors only see the correct "Publication Manifest."

---

How important is this feature?

• 🌗 Medium - can do work without it; but it's important (e.g. to save time or for convenience)

---

When will use cases depending on this become relevant?

• Short-term - 2-4 weeks

[adamjtaylor]

I think this is due to how the config is being generated on deployment (which now happens in a script).
It seems to pick up top-level parents to be included as templates.

I also see the following in the template list that should not be there

• File
• Patient
• Publication

We will need a FAIR ticket to ask how to hide these.

[aclayton555]

@MiekoHash @milen-sage Can we file an issue in FSD for someone on FAIR to look at this?

[MiekoHash]

Thanks for asking, @aclayton555 . Sure, pls go ahead and file a JIRA ticket in FSD space. We will push it through the triage process.

[aclayton555]

@MiekoHash FDS ticket filed here: https://sagebionetworks.jira.com/browse/FDS-408

Thanks!

[aclayton555]

See Jira issue for diagnosis and suggested fix for the HTAN team: https://sagebionetworks.jira.com/browse/FDS-408

Transitioning this to "ready for development." Ideal to tackle in this sprint to resolve this before we focus efforts on multi-tenant DCA testing in June.

[adamjtaylor]

@elv-sb and I have reviewed the proposed fix and have agreed we do not want to do anything regarding changing the deploy action or the config while we are only a short time away from multitenant deployment.

[adamjtaylor]

For 2023-06-28 sprint wrap-up, I think we can move this either to the backlog or to not planned. Consider adding a label multitenant to track issues with this transfer.

[aclayton555]

i'm inclined to put this back in the backlog, and have proceeded to add a "multitenantDCA" label for us to come back to this in an upcoming sprint (regardless of whether it is decided to do/not do work on this) once the multitenant rolls out.