Diagram for project-edition-scene activity

[dirkroorda]

Pure3D data is organised by project, then by edition, then by scene.

An edition consists of one 3D model, i.e. one .glb or .gltf file with 3D data, plus 1 or more accompanying scene files.
Scenes are json files that reflect the initial point of view in a model, but it can also have annotations and metadata of tours, overlays and articles.

We need a detailed view of what to display on project pages, edition pages, and scene pages.

Here is a coarse screenshot of an edition page:

Here you see just one scene and below you see buttons to open the scene in a variety of viewers (here just voyager) and in a variety of versions per viewer. And, if the user is authorised, (s)he can launch the viewer in edit mode by means of the update button.

Questions to be answered:

• Which information to show on the right? Specify for project/edition/scene pages?
• Which (summarized) project information do we display on edition and scene pages?
• Which (summarized) edition information do we display on scene pages?
• Do we provide links to the articles in order to view them outside any 3d viewer? We could make the articles folder navigable.

Questions about editing:

• How should an editing user end an editing session? We could add a button [Save and quit editing].
• If a user wants to edit a scene, but there is already an editing session open for that scene, should we inform the user of the name of the current editor?

[dirkroorda]

@CPapadopoulos84, Susan, can we assign this issue to you?

[CPapadopoulos84]

Responses to Questions about Editing:
Save and Close buttons would work well. Maybe, if you close without saving you can get a message like 'you have unsaved changes. Are you sure you want to close the session'?
Multiple users editing: Yes, it would be good to inform about the user name

[CPapadopoulos84]

For the other question, we will need some time to work on this. To some extend this comes out of our wireframes, but we will need to work a bit more on this.

[dirkroorda]

I noticed that if you have a voyager-story open with unsaved changes and you want to leave the page, you get already a message. Very good of voyager!
And the same should happen for the "close editing button" that we add.

[dirkroorda]

Concerning the other questions:

here is a case where it is easy to overspecify. You can also wait a little, see the evolving backbone, discover its opportunities, and then steer more precisely what information you want to have were.

You could use screenshots of the backbone, use them as wireframes, and annotate them with the things you want to have changed.

[dirkroorda]

We are working hard to get the backbone published on the acceptance server, so that you have the means to do the above.