Replacing Adobe API
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 2
Description
Hello,
I attended the tool's demo today, and the main pain point I heard was getting enough credits for the Adobe API.
Just wondering if you guys are looking into replacing the Adobe API with open-source tools.
Have you looked into https://github.com/opendataloader-project/opendataloader-pdf?
It says auto-tagging is coming in Q2 2026, so worth keeping tabs on.
But it appears it can be used for validation right now.
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 locating the current Adobe API integration and reviewing how PDF validation and auto-tagging are handled. Evaluate whether opendataloader-pdf can replace the existing service, noting that auto-tagging is not available until Q2 2026. Done means a decided replacement approach with validated coverage for the existing workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100