The actions to be done to have a MiniDOMS hosting De Danske Aviser, are listed below (in the sequence in which they need to be done).

1. Identify objects of "De Danske Aviser", design data model (both inter-object structure and on-object metadata).
2. Write object templates for use in the second phase of the two-phase preingester.
3. Prepare release test (describing what should be checked, and what the success criteria are)
4. Set up a semi-permanent test-Fedora, in which we can test-ingest objects via Fedoras Administrator application.
5. Code basic preingester for De Danske Aviser (including only metadata found in filepaths)
   • (Test with actual objects, ingesting a few of the results into test-Fedora by Admin application) Here, the object templates written in an earlier action will be used. Any TODO's in those templates should be finished.
6. Code full preingester for De Danske Aviser (including also metadata from XML-files from collection "De Danske Aviser")
   • (Test with actual objects, ingesting a few of the results into test-Fedora by Admin application)
7. Tweak bundling disseminator
8. Write index- and html-XSLTs (probably letting Summa-people do this)
9. Set up Fedora and Summa-on-a-stick (on-a-server?) on test machine(s)
10. Preingest all objects of "De Danske Aviser"
11. Ingest all (preingested) objects of "De Danske Aviser"
12. Harvest the objects to test-Summa
13. Resolve any issues found when harvesting to test-Summa
14. Perform release test
15. Resolve any remaining issues identified by release test
16. Prepare all real-Summa tasks
17. Release (let the real Summa harvest, perform quick check that things are in order)
18. On wiki, note down where info about how objects look in Fedora can be found. (See "Identify objects" step). This will be useful when we have to ingest the objects in the real DOMS later.
19. Plan who and how to take care of any future bugs / requests from users.