Forks and Editions

[Alex-Jordan]

ORCCA has a significant fork at Lane Community College. Its content is different enough that I think a prospective user should be alerted to its existence.

Also, the PCC ORCCA will evolve into edition 2, but we plan to leave edition 1 available. For other edition evolutions, this would be unnecessary, but in this case the evolution includes significant changes to reflect the local curriculum redesign. And edition 1 is probably still a better option for some prospective adopters.

Both the new fork and a previous edition should ideally be included in pretext-projects, but should not necessarily inherit all of the primary project's attributes.

So what to do about these things? Here is an idea:

1. We already have <project xml:id="pcc-ORCAA">
2. We could have <project xml:id="lane-ORCAA" fork="pcc-ORCAA">
3. We could let item 1 become <project xml:id="pcc-ORCAA" edition="2.0">
4. We could have <project xml:id="pcc-ORCAA" edition="1.0">

In the output HTML, there could just be one entry, with the greatest numerical @edition's information. But there would be an indicator that "this project has forks and/or alternate/previous editions" and clicking something reveals the information about those alternatives.

That's an idea for discussion. But the purpose of this post is to bring attention to doing something for forks and editions.

[rbeezer]

Good suggestions. I'd put translations into the same rough category as forks. What to do with Spanish AATA?

A nice thing about (2) above is that maybe we make a "lighter" entry for the fork/translation and link to the "original" entry since that info/id is present. I might try that with AATA if I get a chance during this push.

I'd put previous editions into the "project responsibility" buckets, or into the project-provided blurb. But have an open mind.