Pauline wrote:
Joshua Hutchinson wrote:
----- Original Message ----- From: Marcello Perathoner <marcello@perathoner.de
It would be useful to include the dp project number in some form. We have a discussion ongoing with Joshua on how to achieve this.
Yep, pretty easy to implement in the teiHeader. And then it can be used by Marcello's script to link back to the DP project commments fairly easily. At this point, I figure it will be in there in the final specs.
Please note there is no 1 to 1 correspondence between the DP projectID & an etext number.
Multi-volume works/works which are split at DP for ease of processing, appear as with a single etext number in PG, while having multiple DP projectIDs.
Not exactly. The only things that don't have a one to one equivalent are the beginner books. Something spans multiple volumes is usually (always?) posted as multiple etexts. There may be an omnibus posting, though, too. I those cases, we'd probably link to the projectID used for the first part going through DP.
DP does record the PG etext number for each projectID once the work has been posted.
DP requires a user be logged in to be able to view the Project Comments pages at present.
i.e. I do not see the wisdom of linking to the internal DP projectID from the PG database.
Whether the link back to DP would be useful or not I leave to others to decide. However, when we get to the point ... someday ... of providing the original page scans (for those that we can), I wouldn't be surprised to see the projectID used as the value to tie back to them. So, let's put the projectID in there for now. It definitely doesn't hurt anything.
It would great to capture the bio. info in some of the DP Project Comments pages in PG, for some of the projects I post process, the DP Project Manager has been adding information to existing wikipedia entries. e.g. http://en.wikipedia.org/wiki/Kermit_Roosevelt
Cheers, P