A share icon is placed next to the title of the work. You can copy the hyperlink to this page here and use that hyperlink in an email or Teams/Slack message. Even easier: as the owner, you can also ask Sidestnd to send an email on your behalf by just supplying the emailaddress of the person who might be interested.
Please note that there are certain situations where people might get notified automatically. For example, if the publication is done on behalf of an organisation, then all the followers and members of this organisation will automatically get a notification that there is a new publication.
When you visit the organisation's page, there is a green bell icon next to the organisation's name. If you click this icon, then you can choose to follow the organisation. From that point on, you'll receive notifications when the organisation publishes new information. These notifications appear in your startpage.
This is handled with "Supporting resources". A supporting resource can be added to a work, to a version within a work, or even to a specific manifestation.
Default behaviour is to open files when possible in the browser. This can be overruled by using the as_attachment flag in a URI, like this ?as_attachment=true
At this moment, Sidestnd is primarily focused on supporting (teams within) a single organisation. In most cases, the number of works is likely to be limited enough that absence of search is not an issue. In the future, a search function might be added for use within organisations or globally for works that are meant for reuse outside organisations.
One of the main FRBR design questions is how to deal with translations. The question is if one thinks that a translation is still the same information but just in a different form, or that it is a new thing. This is almost a philosophical question, and the answer is usually "it depends".
There are three options: create a new work, create a new expression within a work, create a new manifestation. Most often, the middle option is the most appropriate one. However, practical concerns might influence this decision. For example, are there different manifestations of the translation or just a single one? If there is a translation that has different manifestations then it makes sense to turn the translation into a separate state, if only to make the management of the different manifestations easier. The state name can help distinguish this state from the state it was based on, for example "2.1 (Dutch)". If there is just one translated manifestation, then it might be easier to just add this as another manifestation to the existing state, and add a clear description in the manifestation name like "PDF (translation Dutch)".
There are many situations where a file contains references to other files. As the aim is to create something that will work in the future, dependencies that are necessary for processing like schema components must be stored with the main file. This can be done by first creating a ZIP file that contains all required files and then adding this ZIP file as a manifestation.
Adding a ZIP file as a manifestation is useful from a file management perspective. However, it does not make the contents of the ZIP actionable. If I have a schema file that references several shared files, then adding them to a ZIP is a way to capture and "freeze" the state of the schema. At the same time, a schema processor is unlikely to be able to handle the ZIP file - it needs the extracted files.
For this situation, Sidestnd offers the option to extract the files from the ZIP. When uploading a ZIP file, a checkbox can be selected that leads to the creation of two manifestations: the ZIP file itself, and the contents of the ZIP file. A start file inside the ZIP file gets its own URI. If the references to the other files are relative to the startfile, then a processor reading the start file is able to open the components as well.
Sidestnd uses secure_filename() from Werkzeug which only allows:
All other characters, including parentheses, spaces, slashes, and Unicode characters, are removed from the filename.