this is the backend and frontend for the commenting system, I'm not sure about some code in the backend, so any feedback is welcome

This change is 

The item detail has the "CASE Framework URI" with a link. However this is the OpenSALT URI not the CASE URI, but both are useful. Instead display just the UUID as the "Identifier" and have it link to the CASE URI so you can copy the CASE URI.

This pull request reorganizes the columns of the Excel spreadsheet export of frameworks and adds a column for Origin and Destination URI.

This change is 

On drag+drop a framework or the new button #289 bring up a dialog box much like "Make Associations" does and for now to allow users to create a new derivative framework (create IsExactMatchOf relationships but create new identifiers) or Simple Copy (same identifiers, now referenced from the external server). https://opensalt.mybalsamiq.com/projects/opensalt/copy_dialogbox

When generating the smartLevel value, the ExcelExport class does not consider the isChildOf association's sequenceNumber to determine the order and smartLevel of the items.

Some related background

This issue is observed elsewhere as well, sequenceNumber was introduced into the spec quite late and the code has never been fully updated to use it (as it can be difficult at times due to the value not being easily obtained for an item).

Before the sequenceNumber field existed a rank field was added for internal use to allow for ordering items among siblings within OpenSALT. At this point, many areas of the code do not try to use or update the rank field due to (I am assuming) the sequenceNumber being the correct way to handle sibling order. The rank field should probably be removed.

When displaying items there is also an attempt to order by listEnumInSource and humanCodingScheme if there is no specified order.

Closes #568 Closes #471

Related #563

Updates client-side code to display the server-provided uri property value for "Case Framework URL".

Test plan

Manual testing:

1. Import the attached CASE file
2. Browse to the "Test Framework with Imported URIs" Framework
3. Expect that the Document's "Case Framework URL" is http://localhost:3000/uri/https://www.testframeworks.org/doc/1
4. Expect that the Item's "CASE Item URI" (under "More Info") is http://localhost:3000/uri/https://www.testframeworks.org/item/1

case-format-with-uri.json.zip

This change is 

Steps to reproduce:

Case 1:

• move the centre bar to resize the width of the tree and detail sections (wider or narrower)
• resize the browser to be narrower than the centre bar
• ISSUE
  • the height of the page is increased significantly
  • the detail section is missing
  • the "toggle" arrows go missing

Case 2:

• Using the Safari browser on a Mac
• Drag the centre bar left
• ISSUE
  • the "toggle" arrows do not move with the bar

Caused by #263

Primary User Story: As a Super User, I want to configure an external server to be mirrored, and select all or a subset of frameworks on that server to be mirrored, similarly to the mirroring in the CASE network. The only difference is when adding a new mirror you can enter just the server domain and choose to “Mirror all” or “Pick from list”. If you choose to pick from the list, the system should get the list of all frameworks currently on that server and allow you to check one or many of them to mirror individually. If all is selected, when checking for updates, any new frameworks should be automatically added to the mirrors list.

User Story: As a Super User I want remove a mirrored framework, set of frameworks or server.

User Story: As a Super User I want the system to check for changes to a mirrored framework on a defined schedule, and automatically update a mirror if a framework has changed.

User Story: As a Super User I want to see any error in creating or updating a mirror so that I can correct the error. If during an update there is an error, I want the previous mirror(s) cache to continue in use.

In order to implement this feature and storied the JSON Import and Export will need to be remediated to fully comply with the CASE specification

Describe the problem

The pages for managing the various LsDef entities (for example, /cfdef/subject) have no authentication. (They also don't seem to be linked to from anywhere, so administrators don't have an easy way to manage these entities; that's not my main concern with this ticket though.)

Version of OpenSALT

2.1.0

To reproduce

Steps to reproduce the behaviour:

1. Go to '/'
2. Verify you are not logged in
3. Go to /cfdef/subject
4. Click "Create a new entry"
5. Enter some data and click "Create"
   You get a 500 error, but that is unrelated to this bug
6. Return to /cfdef/subject

Expected behaviour

You get a 401 at step 3.

Actual behaviour

After step 6, you can see that the data you entered in step 5 has been created as a new Subject.

Your system (please complete the following information):

• Device: N/A
• OS: N/A
• Browser N/A
• Version: N/A

If you are able to report the URL where an error happened or output from the dev console please do so.

http://localhost:3000/cfdef/subject http://localhost:3000/cfdef/association_grouping http://localhost:3000/cfdef/concept http://localhost:3000/cfdef/grade http://localhost:3000/cfdef/item_type http://localhost:3000/cfdef/licence

Additional context

Besides just requiring authentication, I would expect some sort of authorization on these pages. IMO they should be accessible to all logged-in users, but only superusers should be able to create, edit, or delete entries. I can see that being open to debate though.

When attempting to upload a CSV file to import children, when the button is clicked nothing happens. Unlike this video: https://www.youtube.com/watch?v=7YJAsjZ8BjQ I do not get the next screen when the import button is pressed. No error messages or anything

From 78 to 56 thus far.

https://docs.google.com/spreadsheets/d/1W7301e5vn8F4dEAqxCVvTYqGqOZ1it1vWDOjG1go2bQ/edit#gid=1115616399

https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit #

• [ ] CUSTOM FIELDS: Toggle ACT fields on/off in backend As an OS user with the ability to import/export frameworks
  I want the ability to turn ACT custom fields on/off in the CASE file
  So that we can decide whether they should be included/excluded values in our framework

  SCOPE
  The scope of this story is to have the ability to turn the ACT custom fields on/off on the backend. This functionality will be called 'ACT-CF' as an option. This will allow system admins to determine whether the ACT custom fields should be included/excluded with the CASE file when a framework is imported/exported from OpenSALT.

  OUT OF SCOPE
  Adding the Task Model entity/schema will be completed with KMS-4422
  Adding the ACT Custom Fields to the DB will be completed with KMS-4306
  Adding the Universal Order will be completed with KMS-4431
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Backend capability to support custom fields will be completed with KMS-4338
  Updating the Exporter to support custom fields will be completed with KMS-4346
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES
  Confirm parameter.yml is updated with on/off toggle?

  DOMAIN
  parameters.yml

  DOCUMENTATION
  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

• [ ] CUSTOM FIELDS: Create ACT Custom Fields in DB As a OS user with the ability to import/export frameworks
  I want the ACT Custom Fields added to the DB
  So that we can use them in our framework

  SCOPE
  The scope of this story is to update the DB to include the ACT custom fields in the DB. The list of custom fields include:

  1. Item Taxonomy Codes? Need Brandon to confirm
  2. Statement Origin
  3. Citations Text
  4. Reporting Categories

  OUT OF SCOPE
  Adding the Task Model entity/schema will be completed with KMS-4422
  Adding the Universal Order will be completed with KMS-4431
  Ability to toggle ACT-CF on/off will be completed with KMS-4298
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Backend capability to support custom fields will be completed with KMS-4338
  Updating the Exporter to support custom fields will be completed with KMS-4346
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES
  

  DOMAIN
  OS DB > Table/fieldnames?

  DOCUMENTATION

  Joe's list of custom fields: https://docs.google.com/spreadsheets/d/1kjve-MlAchTFUj_hGsmuYRJG0yG8FGsCrKvKwRDiPGk/edit?invite=CNfD890H&ts=5b17f2ad#gid=0

  https://docs.google.com/spreadsheets/d/1QPaNTcA3na36UmusaTilVp17xkIdJTAXZ1Siisrs0lE/edit#gid=582306884

  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

• [ ] CUSTOM FIELDS: Update backend to read ACT-CF CASE As an OS user with the ability to import/export frameworks
  I want Export Framework backend updated
  So that we can export by ACT-CF and include the ACT custom fields

  SCOPE
  The scope of this story is update the backend to read ACT-CF CASE to allow users to export an ACT-CF Framework successfully.

  OUT OF SCOPE
  Adding the Task Model entity/schema will be completed with KMS-4422
  Adding the ACT Custom Fields to the DB will be completed with KMS-4306
  Adding the Universal Order will be completed with KMS-4431
  Ability to toggle ACT-CF on/off will be completed with KMS-4298
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Updating the Exporter to support custom fields will be completed with KMS-4346
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES
  

  DOMAIN
  OS Landing Page > Select a Framework > Select 'Export' button

  DOCUMENTATION
  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

• [ ] CUSTOM FIELDS: Update Exporter to allow ACT-CF CASE to be exported As an OS user with the ability to import/export frameworks
  I want Export Framework backend updated
  So that we can export by ACT-CF and include the ACT custom fields

  SCOPE
  The scope of this story is update the backend to read ACT-CF CASE to allow users to export an ACT-CF Framework successfully.

  OUT OF SCOPE
  Adding the Task Model entity/schema will be completed with KMS-4422
  Adding the ACT Custom Fields to the DB will be completed with KMS-4306
  Adding the Universal Order will be completed with KMS-4431
  Ability to toggle ACT-CF on/off will be completed with KMS-4298
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Backend capability to support custom fields will be completed with KMS-4338
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES
  

  DOMAIN
  OS Landing Page > Select a Framework > Select 'Export' button

  DOCUMENTATION
  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

• [ ] CUSTOM FIELDS: Create Task Model DB Entity/Schema As a OS user with the ability to import/export frameworks
  I want the DB updated to include the Task Model entity/schema
  So that we can use them to attach to items

  SCOPE
  The scope of this story is to update the DB to allow task models to be added, edited, and deleted. Code will generate a new db table (task models) we should be able to CRUD on the task models. CFItems will be associated to a task model. Assumption is that an item can only have one task model and the task model will only be assigned to a single item.

  OUT OF SCOPE
  Adding the ACT Custom Fields to the DB will be completed with KMS-4306
  Adding the Universal Order will be completed with KMS-4431
  Ability to toggle ACT-CF on/off will be completed with KMS-4298
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Backend capability to support custom fields will be completed with KMS-4338
  Updating the Exporter to support custom fields will be completed with KMS-4346
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES

  1. Precursor: May need to add forms to the UI
  2. Create task model
  3. Edit task model
  4. Delete task model

  DOMAIN
  OS DB > Task_Models

  DOCUMENTATION

  Joe's list of custom fields: https://docs.google.com/spreadsheets/d/1kjve-MlAchTFUj_hGsmuYRJG0yG8FGsCrKvKwRDiPGk/edit?invite=CNfD890H&ts=5b17f2ad#gid=0

  https://docs.google.com/spreadsheets/d/1QPaNTcA3na36UmusaTilVp17xkIdJTAXZ1Siisrs0lE/edit#gid=582306884

  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

• [ ] CUSTOM FIELDS: Universal Order functionality As a OS user with the ability to import/export frameworks
  I want the ability to add a Universal Order to my statements/sub-statements
  So that I view them in order and can re-order them, as needed

  SCOPE
  The scope of this story is to update OS to allow Universal Order to be applied to statements and sub-statements. For Example:

  | Description | Universal
  Order | | --- | --- | | Statement 1 | 1 | | Sub-statement 1 | 2 | | Sub-statement 2 | 3 | | Statement 2 | 4 | | Sub-statement 1 | 5 | | Sub-statement 2 | 6 | | Sub-statement 3 | 7 |

  OUT OF SCOPE
  Adding the Task Model will be completed with KMS-4422
  Ability to toggle ACT-CF on/off will be completed with KMS-4298
  Adding the ACT Customer fields to the DB will be completed with KMS-4306
  Creating a tabbed Item Editor UI will be completed with KMS-4314
  Adding the new tab on Import Framework will be completed with KMS-4322
  Error messaging will be completed with KMS-4330
  Backend capability to support custom fields will be completed with KMS-4338
  Updating the Exporter to support custom fields will be completed with KMS-4346
  Migration of existing data will be completed with KMS-4399

  AUTOMATED ACCEPTANCE TEST CASES
  

  DOMAIN
  OS DB > Table/fieldnames?

  DOCUMENTATION

  Joe's list of custom fields: https://docs.google.com/spreadsheets/d/1kjve-MlAchTFUj_hGsmuYRJG0yG8FGsCrKvKwRDiPGk/edit?invite=CNfD890H&ts=5b17f2ad#gid=0

  https://docs.google.com/spreadsheets/d/1QPaNTcA3na36UmusaTilVp17xkIdJTAXZ1Siisrs0lE/edit#gid=582306884

  https://docs.google.com/document/d/1jPk9ncQqQRD-MqLDBwRADWwH_JHtlVyWbF7tbABpxDc/edit#

custom ACT fields.xlsx (https://act.aha.io/attachments/6537342042452722898/token/08f527244af11ca528f70bda6e46da962385974d799a177218f366473cf509c5.download?size=original)

Created from Aha! https://act.aha.io/features/ACKM-307

Is your feature request related to a problem? Please describe.

Unable to run opensalt on M1 Mac

Feature story

Feature: Add support for M1 Macs for development
  As a developer
  I want to be able to run opensalt on my M1 mac
  So that I can develop against it.

Describe the solution you'd like

The percona image doesn't support the ARM64 platform

Describe alternatives you've considered

mariadb, or building a custom percona docker image that supports multiple platforms

Additional context

console output:

docker-compose up -d
Building db
[+] Building 1.4s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                    0.0s
 => => transferring dockerfile: 296B                                                                                                                    0.0s
 => [internal] load .dockerignore                                                                                                                       0.0s
 => => transferring context: 2B                                                                                                                         0.0s
 => ERROR [internal] load metadata for docker.io/library/percona:8.0                                                                                    1.3s
------
 > [internal] load metadata for docker.io/library/percona:8.0:
------
failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest sha256:30fb648ac9bdcda0b2974c8741d0ac26a00f4d0ab7feb3285b4df0d478576a73: not found
ERROR: Service 'db' failed to build : Build failed
make: *** [docker-start] Error 1```

Describe the problem

When I try to build the docker image for the php service I get an error that it can't find python2 when it attempts to build node-sass.

Version of OpenSALT

I've tried on the latest release tag, and on develop

To reproduce

Steps to reproduce the behaviour:

1. run docker-compose build php

Expected behaviour

It should build the docker image

Actual behaviour

The docker image fails to build due to python being missing

Additional context

It appears to be due to python2 being removed from alpine linux: https://www.alpinelinux.org/posts/Alpine-3.16.0-released.html

partial output from the docker build.

#35 0.476 [1/4] Resolving packages...
#35 0.776 [2/4] Fetching packages...
#35 30.15 [3/4] Linking dependencies...
#35 30.15 warning " > [email protected]" has incorrect peer dependency "node-sass@^4.0.0".
#35 37.52 [4/4] Building fresh packages...
#35 39.08 error /srv/core/node_modules/node-sass: Command failed.
#35 39.08 Exit code: 1
#35 39.08 Command: node scripts/build.js
#35 39.08 Arguments:
#35 39.08 Directory: /srv/core/node_modules/node-sass
#35 39.08 Output:
#35 39.08 Building: /usr/local/bin/node /srv/core/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags=
 --libsass_library=
#35 39.08 gyp info it worked if it ends with ok
#35 39.08 gyp verb cli [
#35 39.08 gyp verb cli   '/usr/local/bin/node',
#35 39.08 gyp verb cli   '/srv/core/node_modules/node-gyp/bin/node-gyp.js',
#35 39.08 gyp verb cli   'rebuild',
#35 39.08 gyp verb cli   '--verbose',
#35 39.08 gyp verb cli   '--libsass_ext=',
#35 39.08 gyp verb cli   '--libsass_cflags=',
#35 39.08 gyp verb cli   '--libsass_ldflags=',
#35 39.08 gyp verb cli   '--libsass_library='
#35 39.08 gyp verb cli ]
#35 39.08 gyp info using [email protected]
#35 39.08 gyp info using [email protected] | linux | arm64
#35 39.08 gyp verb command rebuild []
#35 39.08 gyp verb command clean []
#35 39.08 gyp verb clean removing "build" directory
#35 39.08 gyp verb command configure []
#35 39.08 gyp verb find Python Python is not set from command line or npm configuration```

Create a new or updated view that allows a user to view and navigate a framework, select one or many nodes, and then copy their HCS, Short description and URI/URL to paste into a spreadsheet or document for a complete reference.

Bumps datatables.net from 1.10.23 to 1.11.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This change is 

Thank you for your interest in OpenSALT!

This template helps ensure that we have enough information to work on the issue.
Please feel free to ignore any section that is not applicable or add additional information.

Describe the problem

Added an exemplar with an annotation. Navigating to the Association View does not show the added annotation

Version of OpenSALT

3.1

To reproduce

Steps to reproduce the behaviour:

1. Go to the framework that I created 'Test Framework Vas 1'
2. Add an exemplar for a child item, make sure to add an annotation
3. Click on Association view and select the exemplar checkbox (if not selected)
4. The added exemplar is shown but not the annotation column for this exemplar is empty

Expected behaviour

The annotation that I added in step 2 should be shown on the Association view

Actual behaviour

The annotation is not shown on the Association view for an exemplar

Screenshots

When mirroring case.smarterbalanced.net, there are internal associations between the framework (e.g. the content spec links to the item specs at the target level). Also there are association from the source to items that are resident. In both cases the associations on the left column are not linked. They should be.

see and example here: https://opensalt.net/cftree/item/1127804