Re-using Oracc content for online teaching

As we get ever closer to the new academic year, I’d like to remind you of various ways in which you can re-use the free, open-access cuneiform content on Oracc.org:

1. Basics: Start with http://oracc.org/doc/help/visitingoracc/reusingoracc/index.html for simple ideas that anyone can use without a login: from creating links to lists of texts to embedding whole texts in your own web page. 
2. Next steps: go to http://oracc.org/doc/help/visitingoracc/citingurls/index.html for instructions on linking via key-words and glossary entries if you’re a bit more confident with HTML (again, no login required). 
3. If you have an Oracc login and know how to use it: see my old blog post at https://oracc.blogspot.com/2018/07/creating-proxy-parasite-project.html for guidance on creating your own bespoke “proxy” project if you want to create a whole corpus of texts for your class. For example, an old example of mine, that pulls in material from across many Oracc projects is http://oracc.org/cams/tlab which I built for an undergrad class, “Temple Life in Assyria and Babylonia”, a few years ago. 
4. If you’d like to learn how to make your own “proxy” project but don’t have a login or need a refresher, I’ll be running an interactive online workshop on Thursday 20 August (4pm UK time = 11 am US East Coast, 5pm mainland Europe, 6 pm Iraq, etc). Because I will need to issue Oracc logins in advance, and give proper tutorial support during the session, I have capped attendance at 12 people. Please sign up here: https://www.eventbrite.com/e/oracc-for-online-teaching-tickets-116639651337 and I’ll be in touch with more details. If there’s enough demand, I’ll run extra sessions.

I hope this is all self-explanatory but if you have any questions or problems, please leave me a comment below.

Updated documentation

Over the past week or so I've had a jolly time checking that all the Oracc documentation is up-to-date and reflects current practice, and that all the links work. I won't list every tiny change here, but would like to draw your attention to a few points in particular:

All users: Citing Oracc URLs online and in print

Oracc 2 makes systematic use of stable URIs, so that you can be confident that print references and online links will remain valid. That means, though, that some details of the instructions on how to cite Oracc pages and resources have changed.

Mostly for editors and managers: Oracc language codes

If you have already read my overview of how the new lemmatiser works, you'll know that now you always need to specify Akkadian dialects (unless you are producing ATF for CDLI) and that glossary merges must now always specify the language. I've also worked those changes systematically through the documentation.

For editors and project managers: builder documentation

Editors and project managers will also notice that I have rearranged the list of builder documentation. It's still all there as before but now, I hope, in a more logical order.

For project managers: glossary management

I have incorporated the L2 updates into the sections on glossaries in the pages on project management with Unix and project management with Emacs (and written it into the rest of the documentation).

For project managers: The Oracc Command

This page has been reorganised and updated, so that it is easier to find help on the commands you most need for everyday project management work.

And you'll now find a Documentation full text search at the top of every documentation page.

If you notice anything wrong, broken, missing, or just plain confusing, please let me know, either in the comments or by email. The documentation is for you, the users and project creators, so please tell me if (and how) it isn't serving your needs.