-
Notifications
You must be signed in to change notification settings - Fork 486
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
Move harvestingclient_id from the dataset to dvobject and use it directly for files #9686
Comments
Moved to @siacus backlog column to expedite lingering NIH GREI Year 1 work. |
2023/09/25: Added to 6.1 milestone as per conversation during prioritization meeting. |
2023/10/23: Sized at 10 during sizing meeting. |
The initial PR for this looks good and does what the issue states, that is move the column from one table to another (and modified the code which cares about where this info is for datasets appropriately). However, while reviewing @landreev, @sekmiller and I agreed it would be better if the scope of this issue also encompassed making the relevant changes to the harvesting code to use the moved column for files, that being the motive for this new column. (note: we debated merging the PR and creating a new issue, but in this case it makes more sense to just keep the issue as is intact). So I'm closing the PR and moving this issue to 6.2. With the new scope, it will also need to be resized. |
Also, note, this branch: https://github.com/IQSS/dataverse/tree/9686-move-harvesting-client-id should be the starting point to continue this work. |
2023/12/18
|
Re-opening while discussions on how to proceed are ongoing |
2024/01/31
|
2024/03/13 |
2024/07/10
|
I don't know if it helps or confuses things but @poikilotherm and I were talking about it a bit in Slack yesterday: https://iqss.slack.com/archives/C010LA04BCG/p1720617633778099 |
Description
harvestingclient_id
from the dataset table in the database to the commondvobject
.Revisit/reimplement the concept of a "Harvested file". #8629 (comment)
Any open or closed issues related to this feature request?
The text was updated successfully, but these errors were encountered: