The Authoring action to import a learning design is now changed due to the changes in LDEV-1371* Detecting whether the learning design is of v1.0.2 or v2 is now done at the service* Instead of passing a input stream for the learning design, we pass a File
LDEV-1371: Modify importLearningDesign method to:* Import learning designs directly from the filesystem* Detect whether the design is v1.0.2 or 2.x (moved now to the service instead of the action class)* Modify the error reporting so now the service returns the errors in string lists
Improvements to branch mapping handling and switching branching types (now completed) and warnings when removing activities which are linked to a branching activity
LDEV-1373: Removed the mark altogether from column headings for the learner list - the mark is redundant as the learners' marks are listed, not right/wrong.
LDEV-1373: Put Mark and Question Number on separate lines in class export portfolio to make narrower columns. Then if there are lots of questions, more questions will fit on the normal page width.
LDEV-1221: Delete and rename buttons didn't work in the group folders even though the user owned the learning design. The problem was that the permission returned against each learning design was the permission for the whole folder. Now it is OWNER if the user owns the learning design, or the folder permission otherwise.
LDEV-1348: Fixing the change to add the tool id to the condition - was only getting the id for branching and not for branches, and it was the branches that needed it!
LDEV-1348: Tweaking the hibernate handling of branch activity mappings - can't rely on the cascades to delete unwanted mappings so clear the collection references and delete any unwanted mappings. This is needed when the user changes a branching activity from one type to another (e.g. group based to tool output based).
LDEV-1348: Tweaking the db handling of branch activity mappings. If a user deletes and then readds an identical mapping for grouped based branching, we get a new entry created and the old entry deleted. Can't guarantee what order Hibernate will persist the changes to the db, so e can't have a unique key on group/sequence on the table.
LDEV-1347: Update the validation for branching. Splitting the validation code off into a separate class, to make the LearningDesignService class easier to read.
LDEV-1348: Adding the tool id to the condition, so that conditions can be re-instated automatically in authoring if the user changes a branching activity from tool based to group/teacher chosen and back to tool based. On the server side, the data is redundant at present, so the id is added to the DTO only, and ignored in the extraction code.