include couplet sumaries in public data export

This commit is contained in:
Hamid Reza Mohammadi 2026-09-12 16:06:54 +03:30
parent de3dbeefaa
commit 4920e85e45
2 changed files with 12 additions and 0 deletions

View File

@ -167,6 +167,17 @@ namespace RMuseum.Models.Ganjoor.PublicExport
public int? SectionIndex2 { get; set; } public int? SectionIndex2 { get; set; }
public int? SectionIndex3 { get; set; } public int? SectionIndex3 { get; set; }
public int? SectionIndex4 { get; set; } public int? SectionIndex4 { get; set; }
/// <summary>
/// AI-generated (prefixed "هوش مصنوعی:", matching PoemSummary's own convention) until a
/// human reviews/edits it, at which point the prefix is removed — that prefix's
/// presence/absence is itself the provenance signal, same as for PoemSummary, nothing
/// new needed here to track it. Published specifically so a human editor's curatorial
/// work on a couplet's interpretation — genuinely irreplaceable if the live database
/// were ever lost, unlike the poem text itself, which exists in many other sources —
/// isn't only ever stored in one place.
/// </summary>
public string CoupletSummary { get; set; }
} }
/// <summary> /// <summary>

View File

@ -401,6 +401,7 @@ namespace RMuseum.Services.Implementation
SectionIndex2 = v.SectionIndex2, SectionIndex2 = v.SectionIndex2,
SectionIndex3 = v.SectionIndex3, SectionIndex3 = v.SectionIndex3,
SectionIndex4 = v.SectionIndex4, SectionIndex4 = v.SectionIndex4,
CoupletSummary = v.CoupletSummary,
}).ToList(), }).ToList(),
}; };