Linked objects improvements
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Out of scope for saved search performance related issue, so adding as new:
• Add the user who created the link (how do we handle existing links without that info?)
• Add if a link was created by a saved search
• combine tables in backend so there is one table for all LinkedDVObjects rather than a separate DatasetLinkingDataset and a DatasetLinkingDataverse (the tables are currently identical)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the backend models for LinkedDVObjects, DatasetLinkingDataset, and DatasetLinkingDataverse, then trace how links are created by users and saved searches. Define how existing links without creator metadata are handled and verify that one combined table can represent both link types. Done means creator and saved-search origin are retained and the duplicate tables are consolidated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100