mProjectsCode / mProjectsCode/obsidian-media-db-plugin
Importing a folder per media type instead of per api
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 491
- Forks
- 52
- Avg merge
- 2h 17m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
I've recently done a bulk import of my movies using the "import folder as mediaDB" option and I'm very happy with the results, I would like to do the same for my videogames but the problem is that currently the "import folder as mediaDB" function only has API options instead of media type options. Therefore I can only select the steam API for this and the search often doesn't show the results I want because of all the DLC with a similar name. I'd like to bulk import using OMDB for that reason but currently the bulk import then only search for movies.
Describe the solution you'd like
It would be useful if we could choose the game or movie option when importing a folder so it definitely only searches for games or movies but from multiple APIs, like what was added in #54
Additional context
Another option that would also work would be to exclude DLC from steamAPI search or prioritize actual games so they're at the top.
I'm not sure if I should have posted this as a bug or a feature request
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 tracing the “import folder as mediaDB” flow and compare it with the media-type selection added in #54. Determine where the folder import chooses an API versus a media type. Done means a folder can be imported as games or movies while searching across the relevant APIs, without restricting results to a single API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100