Migrate legacy images #32
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Introduces a dedicated
LegacyImagecollection and migrates legacy images into it, updating image retrieval to rely on this new source.models/LegacyImageMongoose model with indexes; addedLegacyImageTypeScript typescripts/migrate-images.tsto batch-migrate non-eBird images fromHotspot/Groupdocs intoLegacyImage; added npm scriptmigrate-imagesgetHotspotImagesto queryLegacyImage(non-map, non-migrated) instead of embeddedimages, combine with featured ML/eBird images, and updatefeaturedImgaccordinglyImage.lgUrlis now optional to align with legacy recordsWritten by Cursor Bugbot for commit 57b37e2. This will update automatically on new commits. Configure here.