Remove ContentXML field from Tender entity and related repository method
- Eliminated the `ContentXML` field from the `Tender` struct in the entity definition, streamlining the data model. - Removed the `FindTendersWithContentXML` method from the `TenderRepository` interface, as it is no longer necessary. - Updated the `ToTender` method in the `NoticeWorker` to reflect these changes, ensuring consistency across the codebase. This update simplifies the tender data structure and repository interface, improving maintainability and clarity in the tender management system.
This commit is contained in:
@@ -88,7 +88,6 @@ type Tender struct {
|
||||
Source TenderSource `bson:"source" json:"source"`
|
||||
SourceFileURL string `bson:"source_file_url" json:"source_file_url"`
|
||||
SourceFileName string `bson:"source_file_name" json:"source_file_name"`
|
||||
ContentXML string `bson:"content_xml,omitempty" json:"content_xml,omitempty"`
|
||||
ProcessingMetadata ProcessingMetadata `bson:"processing_metadata" json:"processing_metadata"`
|
||||
// AIOverallSummary optional denormalized overall summary for search/list (e.g. synced from AI pipeline storage).
|
||||
AIOverallSummary string `bson:"ai_overall_summary,omitempty" json:"ai_overall_summary,omitempty"`
|
||||
|
||||
Reference in New Issue
Block a user