A searchable document library with exact source references by Xavier Martinez BartraA searchable document library with exact source references by Xavier Martinez Bartra
A searchable document library with exact source referencesXavier Martinez Bartra
Cover image for A searchable document library with exact source references
I’ll build a local search page for up to ten English UTF-8 TXT or Markdown documents, with a combined limit of 20,000 words. It returns matching passages with document and section references so you can inspect the source. You receive the source, run instructions, a manual document-update command and an evaluation report for fifteen supplied queries, including retrieval matches and misses. This is lexical search: it does not generate answers, establish that a passage answers a question or guarantee search correctness or ranking. The tool needs no model subscription. PDF extraction, generated-AI answers, access controls and live integrations can be assessed separately against your documents and environment. To scope the work, provide approved English TXT or Markdown documents within both limits, with unique filenames and usable headings or section labels. Identify the authoritative version of each document. Provide fifteen representative, non-sensitive queries with an expected document/section or an explicit no-answer case. These are evaluation cases, not guaranteed search outcomes. Identify the local operating system and browser, describe the intended document-update process, and confirm that a local tool without login, hosted service or generated answers fits the task. I use OpenAI Codex for AI-assisted development. Before processing your brief or source code with that service, I need confirmation that you have the right to share it and permission covering that material. Customer records and source documents remain local unless you separately identify and authorize content for external AI review. Leaving that authorization blank grants no permission to review document or record content with AI. Do not provide credentials or production personal data. The proposed delivery period starts on a date agreed in writing after the required inputs, permissions and platform contracting steps are complete, following the platform’s actual rules. The package includes 1 consolidated written revision within this scope. Defects against the agreed acceptance checks are corrections; new features, changed rules or extra source material need a separate scope. Briefs, progress updates, revisions and handover are handled in writing.
Starting at$249
Duration4 days
Tags
Python
Data Engineer
Service provided by
Xavier Martinez Bartra Barcelona, Spain
A searchable document library with exact source referencesXavier Martinez Bartra
Starting at$249
Duration4 days
Tags
Python
Data Engineer
Cover image for A searchable document library with exact source references
I’ll build a local search page for up to ten English UTF-8 TXT or Markdown documents, with a combined limit of 20,000 words. It returns matching passages with document and section references so you can inspect the source. You receive the source, run instructions, a manual document-update command and an evaluation report for fifteen supplied queries, including retrieval matches and misses. This is lexical search: it does not generate answers, establish that a passage answers a question or guarantee search correctness or ranking. The tool needs no model subscription. PDF extraction, generated-AI answers, access controls and live integrations can be assessed separately against your documents and environment. To scope the work, provide approved English TXT or Markdown documents within both limits, with unique filenames and usable headings or section labels. Identify the authoritative version of each document. Provide fifteen representative, non-sensitive queries with an expected document/section or an explicit no-answer case. These are evaluation cases, not guaranteed search outcomes. Identify the local operating system and browser, describe the intended document-update process, and confirm that a local tool without login, hosted service or generated answers fits the task. I use OpenAI Codex for AI-assisted development. Before processing your brief or source code with that service, I need confirmation that you have the right to share it and permission covering that material. Customer records and source documents remain local unless you separately identify and authorize content for external AI review. Leaving that authorization blank grants no permission to review document or record content with AI. Do not provide credentials or production personal data. The proposed delivery period starts on a date agreed in writing after the required inputs, permissions and platform contracting steps are complete, following the platform’s actual rules. The package includes 1 consolidated written revision within this scope. Defects against the agreed acceptance checks are corrections; new features, changed rules or extra source material need a separate scope. Briefs, progress updates, revisions and handover are handled in writing.
$249