Add retirement dates for sets already retired #37

New Issue

jonaskp · 2025-01-06T23:27:46+01:00

jonaskp commented

2025-01-06 23:27:46 +01:00

Current implementation of retirement date pulls data from a source that tracks upcoming retirements.
This means that when adding a set to wishlist which is already retired, retirement date will not be picked up, and field will be empty.

Feature request is to find a data source that has retirement dates for already retired sets, and add this date to the wishlist.
Brickset and Rebrickable seems to have "to"/"exit"-dates for retired sets.

Additional: Colorcoding the retirement dates: ie. Yellow for upcoming retirements, red for already retired sets.

Example set already retired: Set 10185:
https://brickset.com/sets/10185-1/Green-Grocer
https://rebrickable.com/sets/10185-1/green-grocer/

Current implementation of retirement date pulls data from a source that tracks upcoming retirements. This means that when adding a set to wishlist which is already retired, retirement date will not be picked up, and field will be empty. Feature request is to find a data source that has retirement dates for already retired sets, and add this date to the wishlist. Brickset and Rebrickable seems to have "to"/"exit"-dates for retired sets. Additional: Colorcoding the retirement dates: ie. Yellow for upcoming retirements, red for already retired sets. Example set already retired: Set 10185: https://brickset.com/sets/10185-1/Green-Grocer https://rebrickable.com/sets/10185-1/green-grocer/

👍 1

FrederikBaerentsen commented

2025-01-19 08:22:56 +01:00

Retirement date is unfortunately not part of the rebrickable api, which is why it is implemented differently.

FrederikBaerentsen added the

Kind/Enhancement

label 2025-01-19 08:23:02 +01:00

jonaskp commented

2025-01-19 08:30:56 +01:00

Ahh, Thought it might only be the “future retirement” that wasn’t there, from how I read the initial discussion on this feature.

So it would need to implement another source (for instance Brickset, which I dont know about, so not even sure if it has api or it would work).

As a possible workaround, maybe make it so retirement date, once it has been pickee up by current implementation, is not deleted from BrickTracker again, once it is removed from the spreadsheet.

That Way, it would atleast Track previously reirement of sets you added before they were retired.

Not sure if it already Works this Way now.

Ahh, Thought it might only be the “future retirement” that wasn’t there, from how I read the initial discussion on this feature. So it would need to implement another source (for instance Brickset, which I dont know about, so not even sure if it has api or it would work). As a possible workaround, maybe make it so retirement date, once it has been pickee up by current implementation, is not deleted from BrickTracker again, once it is removed from the spreadsheet. That Way, it would atleast Track previously reirement of sets you added before they were retired. Not sure if it already Works this Way now.

FrederikBaerentsen commented

2025-01-19 10:36:34 +01:00

Rebrickable gives this info in their API:

{
  "set_num": "10185-1",
  "name": "Green Grocer",
  "year": 2008,
  "theme_id": 155,
  "num_parts": 2358,
  "set_img_url": "https://cdn.rebrickable.com/media/sets/10185-1/70981.jpg",
  "set_url": "https://rebrickable.com/sets/10185-1/green-grocer/",
  "last_modified_dt": "2016-04-23T11:53:18.502825Z"
}

Which unfortunately isn't a lot compared to what's available on their site.

It looks like Brickset does offer a launch and retirement date in their API, but getting an API key is a manual application and not automatic, which makes it harder.

Saving previous dates could work. I will keep the issue open and add it as an idea for future improvements.

Rebrickable gives this info in their API: ````json { "set_num": "10185-1", "name": "Green Grocer", "year": 2008, "theme_id": 155, "num_parts": 2358, "set_img_url": "https://cdn.rebrickable.com/media/sets/10185-1/70981.jpg", "set_url": "https://rebrickable.com/sets/10185-1/green-grocer/", "last_modified_dt": "2016-04-23T11:53:18.502825Z" } ```` Which unfortunately isn't a lot compared to what's available on their site. It looks like Brickset does offer a launch and retirement date in their API, but getting an API key is a manual application and not automatic, which makes it harder. Saving previous dates could work. I will keep the issue open and add it as an idea for future improvements.

👍 1

FrederikBaerentsen added this to the General Improvements project 2025-01-19 10:36:41 +01:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#37