-
Notifications
You must be signed in to change notification settings - Fork 11
feat: add document management metadata documentation #328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
6b03448 to
beb7c5f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds comprehensive documentation for the Document Management Integration, specifically covering metadata structure and API endpoints for document upload and revision operations.
Changes:
- Added detailed metadata field reference documentation covering standard, system, placeholder, workflow, and custom fields
- Added API endpoints reference page with links to all Document Management endpoints
- Included examples of field types, value structures, and complete API response
Reviewed changes
Copilot reviewed 1 out of 1 changed files in this pull request and generated 8 comments.
| File | Description |
|---|---|
| document_management_integration/document_management_metadata_details.md | Comprehensive documentation of document metadata structure, field types, value sources, and integration processing with example responses |
| document_management_integration/document_management_api_endpoints.md | Quick reference table of Document Management API endpoints with descriptions and URIs |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
document_management_integration/document_management_metadata_details.md
Outdated
Show resolved
Hide resolved
beb7c5f to
8ee7c64
Compare
8ee7c64 to
02321f5
Compare
| | **placeholder_assignee** | reference | Assignee of the placeholder document. | | ||
| | **placeholder_due_date** | timestamp | Due date of the placeholder document. | | ||
| | **project** | reference | An abbreviation of the project's name. | | ||
| | **project_stage** | lov_entry | The construction stage associated with the document. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this field type is a reference:
| | **project_stage** | lov_entry | The construction stage associated with the document. | | |
| | **project_stage** | reference | The construction stage associated with the document. | |
| | **timestamp** | Date and time in ISO 8601 UTC format | | ||
| | **lov_entry** | Single selection from project-configured list of values | | ||
| | **lov_entries** | Multiple selections from project-configured list of values | | ||
| | **reference** | Link to another entity such as users, locations, or workflows | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is also a numeric field type
| | **SCRAPING_FAILED** | Filename scraping was attempted but failed for this field | Yes - can be set manually | | ||
| | **ML** | Value populated by Machine Learning analysis | Yes - manual values override | | ||
| | **ML_FAILED** | ML analysis was attempted but failed for this field | Yes - can be set manually | | ||
| | **SYSTEM** | Value set by Document Management system automatically | Depends on field | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could call out these are not user-overridable:
| | **SYSTEM** | Value set by Document Management system automatically | Depends on field | | |
| | **SYSTEM** | Value set by Document Management system automatically | No -system fields cannot be modified | |
|
|
||
| ## Field Type Reference | ||
|
|
||
| In the Document Upload and Document Revision API responses, each field object in the `fields` array includes a `type` property that determines its value format and structure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider possibly linking the API documentation
| *** | ||
| <details> | ||
| <summary class="collapseListTierOne">Overview of document metadata fields</summary> | ||
| <pre><code>{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I preview this code block, the formatting is off for some reason.
| ```json | ||
| { | ||
| "integrationStatuses": { | ||
| "ML": "in_progress" | "completed" | "error" | "not_applicable", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using a comment for enum values. It currently renders invalid syntax highlighting :
| "ML": "in_progress" | "completed" | "error" | "not_applicable", | |
| "ML": "in_progress", // One of: in_progress, completed, error, not_applicable |
Jira Ticket:
🎫 DOCINT-1056
Summary
Adds documentation for PDM metadata.
Change Type(s)