Thanks for getting on touch on here - it will be quite useful to answer these questions with other schools being able to see the responses too (with Markbook being so new)!
I'll go through each of the issues/questions by quoting the questions below (with my response).
The first 2 posts (about the Markschemes):
1.) I'm not sure why inactive Markschemes are still showing in the Markschemes selector - this component in the Markbook creator wizard should only be looking at active Markschemes (that have been turned on). I will take a look at your platform and see if I can find out what is happening here, and raise a bug if I can rep that.
2.) The Markbook creator only allows you to create a Markbook when it is happy with all of the parameters. It looks like it could be something odd going on with the Markscheme selected that is preventing it from accepting it. This explains why when you go to use the 'Create and Add to Markbook' button in the Assignment List (for an assignment that is 'Not in a Markbook', in the screenshot you showed one using the 'Percentage' markschemes - which definitely won't have any issues....... I'll try and rep this now and get back to you on it / raise a bug.
As Graham alluded to, it looks like there is an issue with the cycles and periods on your platform. With the introduction of the Markbook (Mozart release) we have added an element of FrogProgress, which brings in the concept of Cycles and Periods. Cycles are essentially Academic Years, and Periods are Half terms - you can see this new section in System Preferences > Assessment Cycles & Targets.
The Markbooks section of the Markbook app make use of these to allow Teachers to organise their assignments per Academic Year. Currently the Markbooks will show everything from this Academic Year - and we will be working on implementing an Academic Year roller later this Academic Year to allow schools to go back to previous years, in preparation for September. This will unfortunately mean that any assignments created before this Academic Year will not display in the Markbooks though (although you can still access them in the Assignments list / tab.
There is a script that runs when you get the Mozart release, which should add a default Academic Year with periods - running from September 18 to September 19 - however this doesn't look to have worked properly on your platform, as that is saying the Academic Year started last week! (which is why you're not seeing Assignments previous to that week appearing in the Markbooks). It looks like some schools MIS systems send through Academic Years, which are being stored in the database and conflicting with the script.
We've got a bug raised with this, and are looking to fix this for schools in general, however I have manually gone in and added the default Cycle and Period which the script should have done for you - so you should now see all of this year's (since the start of September) assignments in Markbooks.
We have gone with this order to encourage schools to keep on top of homework, and the ordering reflects the ordering in the MyFrog section (based on 'Due date' nearest at the top descending. From the schools we've spoken to already, they do share your opinion - particularly for the Closed Assignments.
Currently, if you click the 'Issue Date' column header at the top, it will sort the Assignments they way you want:
The problem is that currently you would need to do that each time you access the app (it doesn't remember).
Would a solution of ensuring this 'sorting' is remembered the next time you access the app (even if you log out) be good enough to solve this problem for you?
For this - there is the logic applied that if a student hands in the work themselves after the due date - it will be flagged as 'Late'. However when a teacher hands the work in on their behalf - it should never add the late flag unless they specifically click the 'late' button. Thanks for flagging this (excuse the pun) I have raised a bug and hopefully it can get sorted ASAP!
Hope this addresses all of the issues you mentioned! Let me know if not, or if you have any further questions.