tlg2200.tlg (Libanius)-different IDS for the same work in First1K vs. the Perseus Catalog

[AlisonBabeu]

So this is an old problem with multiple components that I'm not sure has a practical solution, but as I'm updating a lot of metadata records and also trying to create catalog records for everything in Scaife I thought I would try and spell it out here.

The orations of Libanius within the TLG is just one work tlg2200.tlg004, but one that was split up for the Perseus Catalog.
For lack of a better solution, I used the extension x01, x02, etc. to create subworks for within the orations, so I ended up with identifiers such as
tlg2200.tlg004x01 for Oratio 1
tlg2200.tlg004x02 for Oratio 2

These identifiers didn't work for creating valid URNs for First1K/Scaife so the orations ended up with the following:
urn:cts:greekLit:tlg2200.tlg00401.opp-grc1
urn:cts:greekLit:tlg2200.tlg00402.opp-grc1

There are 64 orations that follow this pattern. The same issue happened with the 55 Declamations (tlg2200.tlg005), with works in the catalog with identifiers such as tlg2205.tlg005x01 and works in Scaife urn:cts:greekLit:tlg2200.tlg00501.opp-grc1.

I'm not sure if this really matters or even why I am feeling the need to spell it out after it has stood for so many years, but since I was going to update the 1st1K works of Libanius to have the 1st1K URNs rather than "opp" ones at this point I wasn't sure if it was worth revisiting, since I don't like the idea of the same work having two different identifiers within the metadata.

[lcerrato]

What about a, b, c, etc.? That seems a better way of representing parts of a larger work.
If the URNs are already being changed that seems more intuitive than the "x01" designation.
I don't know how any of this affects links to these works, though.

[AlisonBabeu]

hi @lcerrato on the whole that was what I started doing soon afterwards with works of this sort, I think it is probably best to leave the IDS. At least the new way that catalog data is created I can create expression records for each of these and store them within one larger work record. Thanks for taking a look.