Skip to content

Determine procedure for nested ROR entities #72

@bryanmgee

Description

@bryanmgee

Many funders have specific institutes/centers/divisions/directorates/programs that have their own ROR. With the current interface, recording only the highest-level ROR would make the most sense, but there is likely going to be demand for (a) more granular metadata, which is hard/impossible to obtain if it is not collected initially; and (b) functionality to aggregate child RORs under a query for a parent ROR.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions