File-to-DB graph import results in loss of embedded asset alt text
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Search first
- [x] I searched and no similar issues were found
### What Happened?
I migrated from OG to DB only to find all my embedded asset alt texts had not survived the migration
### Reproduce the Bug
1. In Logseq OG 1.0.0
1. Add new graph "Temp"
2. Create new page "This Is the Page Name"
3. Add file "this-is-the-file-name.pdf" to page
4. Edit alt text (see screenshot)
1. From "this-is-the-file-name.pdf"
2. To "This is the alt text"
2. In Logseq 2.0.1
1. "Import existing notes" → "File to DB graph"
2. Select Temp graph from step 1.1
3. Select "Submit" to import
4. Navigate to page This Is the Page Name
### Expected Behavior
On the page imported from OG to DB, the alt text is completely gone (see screenshot), replaced by the asset name.
When importing, could the asset name be set to the alt text instead of the file name?
I don't want to lose the alt next on all my assets when migrating to Logseq DB
### Screenshots
## In Logseq OG
## In Logseq DB
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
OS: Kubuntu 26.04
Source: Desktop Logseq OG 1.0.0 (revision 680b371)
Destination: Desktop Logseq 2.0.1 (revision b09316a)
### Additional Context
Installed plugins:
- Bullet Threading
- Journals calendar
Result is the same with these plugins disabled
Dev tools console has no errors
### Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
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 reproducing the described OG 1.0.0 to DB 2.0.1 migration through “Import existing notes” → “File to DB graph,” using an embedded asset with edited alt text. Trace that import flow to find where the asset name replaces the alt text; done means the imported page preserves the original alt text instead of the file name.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100