From 71c5a8ef16f6dd9398e3195b49bd987fd5dd174d Mon Sep 17 00:00:00 2001 From: Felix Date: Tue, 27 Jan 2026 12:24:53 +0100 Subject: [PATCH 01/29] #2345 added function that removes tags around abstract --- .../src/routes/importjson/+page.svelte | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte index fc30602f1..131b62453 100644 --- a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte +++ b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte @@ -302,6 +302,11 @@ // apply custom rules from transformations.ts const transformedData = applyTransformations(data); + // remove tags in descr + if (transformedData.abstract) { + transformedData.abstract = stripJatsTags(transformedData.abstract); + } + // Filter data based on mapping.json validatedData.data = filterData(transformedData, mapping); @@ -418,6 +423,15 @@ } + function stripJatsTags(value: string): string { + if (!value) return value; + return value + .replace(/]*>/gi, "") + .replace(/<\/jats:p>/gi, "") + .trim(); + } + + /* ============================================================ FILTER DATA ACCORDING TO MAPPING.JSON From 426a7834c9a5dfb9e0b507b67d252edcbcb535f6 Mon Sep 17 00:00:00 2001 From: geofranzi Date: Tue, 27 Jan 2026 21:41:38 +0100 Subject: [PATCH 02/29] Remove formatting within subjects of emails #2356 --- .../Utilities/MessageHelper.cs | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Components/AAA/BExIS.Security.Services/Utilities/MessageHelper.cs b/Components/AAA/BExIS.Security.Services/Utilities/MessageHelper.cs index 503d11de4..0702f4e61 100644 --- a/Components/AAA/BExIS.Security.Services/Utilities/MessageHelper.cs +++ b/Components/AAA/BExIS.Security.Services/Utilities/MessageHelper.cs @@ -160,7 +160,7 @@ public static string GetSendRequestMessage(long datasetid, string title, string public static string GetWithdrawRequestHeader(long datasetid, string requester) { - return $"Data request from {requester} for dataset with ID {datasetid} withdrawn"; + return $"Data request from {requester} for dataset with ID {datasetid} withdrawn"; } public static string GetWithdrawRequestMessage(long datasetid, string title, string requester) @@ -173,7 +173,7 @@ public static string GetWithdrawRequestMessage(long datasetid, string title, str public static string GetAcceptRequestHeader(long datasetid, string requester) { - return $"Data request from {requester} for dataset with ID {datasetid} granted"; + return $"Data request from {requester} for dataset with ID {datasetid} granted"; } public static string GetAcceptRequestMessage(long datasetid, string title) @@ -186,7 +186,7 @@ public static string GetAcceptRequestMessage(long datasetid, string title) public static string GetRejectedRequestHeader(long datasetid, string requester) { - return $"Data request from {requester} for dataset with ID {datasetid} rejected"; + return $"Data request from {requester} for dataset with ID {datasetid} rejected"; } public static string GetRejectedRequestMessage(long datasetid, string title) @@ -342,7 +342,7 @@ public static string GetUnsetPublicMessage(string userName, long datasetid, stri public static string GetPushApiStoreHeader(long datasetid, string title) { - return $"Receive data for dataset '{title}' with ID {datasetid}"; + return $"Receive data for dataset '{title}' with ID {datasetid}"; } public static string GetPushApiStoreMessage(long datasetid, string userName, string[] errors = null) @@ -386,7 +386,7 @@ public static string GetPushApiValidateMessage(long datasetid, string userName, public static string GetPushApiUploadSuccessHeader(long datasetid, string title) { - return $"Upload completed for dataset: '{title}' with ID {datasetid}"; + return $"Upload completed for dataset: '{title}' with ID {datasetid}"; } public static string GetPushApiUploadSuccessMessage(long datasetid, string userName) @@ -396,7 +396,7 @@ public static string GetPushApiUploadSuccessMessage(long datasetid, string userN public static string GetPushApiUploadFailHeader(long datasetid, string title) { - return $"Upload was not successful for dataset '{title}' with ID {datasetid}"; + return $"Upload was not successful for dataset '{title}' with ID {datasetid}"; } public static string GetPushApiUploadFailMessage(long datasetid, string userName, string[] errors) From 20cf2283e6705cb78f2fb1baae686d4abcee787f Mon Sep 17 00:00:00 2001 From: geofranzi Date: Tue, 27 Jan 2026 22:59:25 +0100 Subject: [PATCH 03/29] Links to non-open datasets (datasets without release/major tag) - change text #2342 --- .../DDM/BExIS.Modules.Ddm.UI/Controllers/DataController.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/DataController.cs b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/DataController.cs index 93644c5c2..e4886ccea 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/DataController.cs +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/DataController.cs @@ -260,7 +260,7 @@ public ActionResult ShowData(long id, int version = 0, bool asPartial = false, s // Throw error if no version id was found. if (versionId <= 0) { - ModelState.AddModelError("", string.Format("The version with the requested name {1} or id {0} does not exist or is not publicly accessible", version, versionName)); + ModelState.AddModelError("", string.Format("The requested version (release tag or version ID: {0}{1}) could not be found or you don’t have permission to access it.", version, versionName)); } else { From 20a92654d50667b159481dc24d793beaf8405224 Mon Sep 17 00:00:00 2001 From: geofranzi Date: Wed, 28 Jan 2026 21:52:43 +0100 Subject: [PATCH 04/29] Metadata API: Add update/change comment #2360 --- .../Controllers/API/MetadataInController.cs | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/MetadataInController.cs b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/MetadataInController.cs index f1fcfcf3d..252e6949b 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/MetadataInController.cs +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/MetadataInController.cs @@ -73,6 +73,7 @@ public async Task Put(int id) var request = Request.CreateResponse(); User user = null; string error = ""; + string comment = "Update via API"; DatasetManager datasetManager = new DatasetManager(); UserManager userManager = new UserManager(); @@ -207,6 +208,12 @@ public async Task Put(int id) { return Request.CreateErrorResponse(HttpStatusCode.ExpectationFailed, "the json does not have the expected structure"); } + + var commentProperty = metadataJson.Property("@comment"); + if (commentProperty != null && commentProperty.Value != null && commentProperty.Value.ToString().Length > 0) + { + comment = commentProperty.Value.ToString(); + } } else { @@ -254,12 +261,12 @@ public async Task Put(int id) workingCopy.ModificationInfo = new EntityAuditInfo() { Performer = user.UserName, - Comment = "via API", - ActionType = AuditActionType.Create + Comment = "Metadata", + ActionType = AuditActionType.Create, }; datasetManager.EditDatasetVersion(workingCopy, null, null, null); - datasetManager.CheckInDataset(id, "via API", user.Name, ViewCreationBehavior.None); + datasetManager.CheckInDataset(id, comment, user.Name, ViewCreationBehavior.None); } LoggerFactory.LogData(id.ToString(), typeof(Dataset).Name, Vaiona.Entities.Logging.CrudState.Created); From c67ba7ca76d3d0f892f86e8d842982f0a50c376b Mon Sep 17 00:00:00 2001 From: geofranzi Date: Wed, 28 Jan 2026 22:59:05 +0100 Subject: [PATCH 05/29] Update core ui #2321 --- Console/BExIS.Web.Shell.Svelte/package.json | 2 +- .../Areas/DCM/BExIS.Modules.Dcm.UI.Svelte/package.json | 3 ++- .../Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/package.json | 2 +- .../Areas/DIM/BExIS.Modules.Dim.UI.Svelte/package.json | 2 +- .../Areas/PUM/BExIS.Modules.Pum.UI.Svelte/package.json | 2 +- .../Areas/RPM/BExIS.Modules.Rpm.UI.Svelte/package.json | 2 +- 6 files changed, 7 insertions(+), 6 deletions(-) diff --git a/Console/BExIS.Web.Shell.Svelte/package.json b/Console/BExIS.Web.Shell.Svelte/package.json index 7631b994d..4f43fac14 100644 --- a/Console/BExIS.Web.Shell.Svelte/package.json +++ b/Console/BExIS.Web.Shell.Svelte/package.json @@ -52,7 +52,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@sveltejs/adapter-static": "3.0.2", "buffer": "6.0.3", "gray-matter": "4.0.3", diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI.Svelte/package.json b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI.Svelte/package.json index 0fc8b844a..cdd921269 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI.Svelte/package.json +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI.Svelte/package.json @@ -34,6 +34,7 @@ "@types/node": "22.0.2", "@typescript-eslint/eslint-plugin": "8.0.0", "@typescript-eslint/parser": "8.0.0", + "@ts4nfdi/terminology-service-suite-js": "^6.0.0", "autoprefixer": "10.4.19", "eslint": "9.8.0", "eslint-config-prettier": "9.1.0", @@ -50,7 +51,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@bexis2/bexis2-rpm-ui": "0.2.15", "@floating-ui/dom": "1.6.8", "@fortawesome/free-solid-svg-icons": "6.6.0", diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/package.json b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/package.json index ef0799109..82659ad45 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/package.json +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/package.json @@ -50,7 +50,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@floating-ui/dom": "1.6.8", "@fortawesome/free-solid-svg-icons": "6.6.0", "@sveltejs/adapter-static": "3.0.2", diff --git a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI.Svelte/package.json b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI.Svelte/package.json index 2a58d2152..66ef561e5 100644 --- a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI.Svelte/package.json +++ b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI.Svelte/package.json @@ -50,7 +50,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@floating-ui/dom": "1.6.8", "@fortawesome/free-solid-svg-icons": "6.6.0", "@sveltejs/adapter-static": "3.0.2", diff --git a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/package.json b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/package.json index 6dfaafbea..325688ffa 100644 --- a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/package.json +++ b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/package.json @@ -52,7 +52,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@floating-ui/dom": "1.6.8", "@fortawesome/free-solid-svg-icons": "6.6.0", "@sveltejs/adapter-static": "3.0.2", diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI.Svelte/package.json b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI.Svelte/package.json index 046542758..4cc6d95a4 100644 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI.Svelte/package.json +++ b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI.Svelte/package.json @@ -51,7 +51,7 @@ }, "type": "module", "dependencies": { - "@bexis2/bexis2-core-ui": "0.4.64", + "@bexis2/bexis2-core-ui": "0.4.65", "@floating-ui/dom": "1.6.8", "@sveltejs/adapter-static": "3.0.2", "@sveltejs/package": "2.3.2", From 3b824d76857740ec78b39e7a93bbb81c1f797129 Mon Sep 17 00:00:00 2001 From: geofranzi Date: Wed, 28 Jan 2026 23:32:49 +0100 Subject: [PATCH 06/29] Fix Publications added via API are shown under datasets and not under publications in My Data #2359 --- .../BExIS.Modules.Dcm.UI/Controllers/API/DatasetInController.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/DatasetInController.cs b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/DatasetInController.cs index e5bd0129a..299db46b1 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/DatasetInController.cs +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/API/DatasetInController.cs @@ -135,7 +135,7 @@ public HttpResponseMessage Post([FromBody] PostApiDatasetModel dataset) datasetId = newDataset.Id; // add security - entityPermissionManager.CreateAsync(user.UserName, "Dataset", typeof(Dataset), newDataset.Id, Enum.GetValues(typeof(RightType)).Cast().ToList()); + entityPermissionManager.CreateAsync(user.UserName, entityTemplate.EntityType.Name, typeof(Dataset), newDataset.Id, Enum.GetValues(typeof(RightType)).Cast().ToList()); //add title and description to the metadata From 9a023213d711edf80ea7ed757415203b2c3671c9 Mon Sep 17 00:00:00 2001 From: geofranzi Date: Wed, 28 Jan 2026 23:46:28 +0100 Subject: [PATCH 07/29] Add operation for PUM and metadiff #2295 #2164 --- database update scripts/4.2.1-4.3.0.sql | 26 +++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 database update scripts/4.2.1-4.3.0.sql diff --git a/database update scripts/4.2.1-4.3.0.sql b/database update scripts/4.2.1-4.3.0.sql new file mode 100644 index 000000000..02440faa1 --- /dev/null +++ b/database update scripts/4.2.1-4.3.0.sql @@ -0,0 +1,26 @@ +BEGIN TRANSACTION; + +-- BEXIS2 Version Update +INSERT INTO public.versions( + versionno, extra, module, value, date) + VALUES (1, null, 'Shell', '4.3.0',NOW()); + +INSERT INTO public.operations (versionno, extra, module, controller, action, featureref) +SELECT 1, NULL, 'DDM', 'metadiff', '*', null +WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='DDM' AND controller='metadiff'); + +INSERT INTO public.operations (versionno, extra, module, controller, action, featureref) +SELECT 1, NULL, 'PUM', 'importcsv', '*', null +WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='PUM' AND controller='importcsv'); + +INSERT INTO public.operations (versionno, extra, module, controller, action, featureref) +SELECT 1, NULL, 'PUM', 'importjson', '*', null +WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='PUM' AND controller='importjson'); + +INSERT INTO public.operations (versionno, extra, module, controller, action, featureref) +SELECT 1, NULL, 'PUM', 'view', '*', null +WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='PUM' AND controller='view'); + + + +commit; From 36785976744528a0be38a9807ba41396810ee012 Mon Sep 17 00:00:00 2001 From: geofranzi Date: Thu, 29 Jan 2026 00:07:45 +0100 Subject: [PATCH 08/29] Dataset Versions API: Add change description #2362 --- .../BExIS.Modules.Dim.UI/Controllers/API/DatasetOutController.cs | 1 + .../Areas/DIM/BExIS.Modules.Dim.UI/Models/API/ApiModels.cs | 1 + 2 files changed, 2 insertions(+) diff --git a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/API/DatasetOutController.cs b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/API/DatasetOutController.cs index d940f4196..f4b5c1530 100644 --- a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/API/DatasetOutController.cs +++ b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/API/DatasetOutController.cs @@ -74,6 +74,7 @@ public IEnumerable Get() Number = i + 1 }; if(dsv.Tag != null) datasetVersionModel.Tag = dsv.Tag.Nr; + if(dsv.ChangeDescription != null) datasetVersionModel.ChangeDescription = dsv.ChangeDescription; datasetModel.Versions.Add(datasetVersionModel); diff --git a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Models/API/ApiModels.cs b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Models/API/ApiModels.cs index cc6a7fbf2..25e7dff01 100644 --- a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Models/API/ApiModels.cs +++ b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Models/API/ApiModels.cs @@ -21,6 +21,7 @@ public class ApiSimpleDatasetVersionModel public long Id { get; set; } public long Number { get; set; } public double Tag { get; set; } + public string ChangeDescription { get; set; } } /// From 5af333a7313545bdf5114b7161e5648f63b4a0b0 Mon Sep 17 00:00:00 2001 From: Franziska Zander Date: Thu, 29 Jan 2026 13:45:53 +0100 Subject: [PATCH 09/29] Curation Tool: Feature permissions missing in update script - add operation #2294 --- database update scripts/4.2.1-4.3.0.sql | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/database update scripts/4.2.1-4.3.0.sql b/database update scripts/4.2.1-4.3.0.sql index 02440faa1..7ad1bf631 100644 --- a/database update scripts/4.2.1-4.3.0.sql +++ b/database update scripts/4.2.1-4.3.0.sql @@ -21,6 +21,8 @@ INSERT INTO public.operations (versionno, extra, module, controller, action, fea SELECT 1, NULL, 'PUM', 'view', '*', null WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='PUM' AND controller='view'); - +INSERT INTO public.operations (versionno, extra, module, controller, action, featureref) +SELECT 1, NULL, 'DDM', 'curation', '*', null +WHERE NOT EXISTS (SELECT * FROM public.operations WHERE module='DDM' AND controller='curation'); commit; From 10c825795442ac9f12b4975017a62ed79e9822f3 Mon Sep 17 00:00:00 2001 From: david schoene Date: Fri, 30 Jan 2026 11:41:46 +0100 Subject: [PATCH 10/29] 2299 remove module help links and add custom help links in generals --- .../App_Data/BExIS.Web.Shell.xml | 9 + .../Areas/BAM/BAM.Manifest.xml | 5 +- .../Areas/BAM/BExIS.Modules.Bam.UI.csproj | 3 - .../Areas/BAM/Bam.Settings.json | 7 - .../Areas/BAM/Controllers/HelpController.cs | 19 -- .../Areas/BAM/Views/Help/Index.cshtml | 98 ------ .../Areas/BAM/Views/Help/Informations.xml | 16 - .../BExIS.Modules.Dcm.UI.csproj | 3 - .../Controllers/Legacy/HelpController.cs | 19 -- .../DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml | 5 - .../BExIS.Modules.Dcm.UI/Dcm.Settings.json | 8 +- .../Views/Help/Index.cshtml | 290 ------------------ .../Views/Help/Informations.xml | 39 --- .../BExIS.Modules.Ddm.UI.csproj | 3 - .../Controllers/HelpController.cs | 20 -- .../DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml | 5 - .../BExIS.Modules.Ddm.UI/Ddm.Settings.json | 7 - .../Views/Help/Index.cshtml | 13 - .../Views/Help/Information.xml | 81 ----- .../BExIS.Modules.Dim.UI.csproj | 3 - .../Controllers/HelpController.cs | 19 -- .../DIM/BExIS.Modules.Dim.UI/Dim.Manifest.xml | 4 - .../BExIS.Modules.Dim.UI/Dim.Settings.json | 7 - .../Views/Help/Index.cshtml | 197 ------------ .../Views/Help/Informations.xml | 21 -- .../BExIS.Modules.Rpm.UI.csproj | 1 - .../Controllers/HelpController.cs | 17 - .../RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml | 5 - .../BExIS.Modules.Rpm.UI/Rpm.Settings.json | 7 - .../BExIS.Modules.Sam.UI.csproj | 3 - .../Controllers/HelpController.cs | 16 - .../SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml | 4 - .../BExIS.Modules.Sam.UI/Sam.Settings.json | 7 - .../Views/Help/Index.cshtml | 143 --------- .../Views/Help/Informations.xml | 108 ------- .../Areas/VIM/BExIS.Modules.Vim.UI.csproj | 3 - .../Areas/VIM/Controllers/HelpController.cs | 19 -- .../Areas/VIM/Views/Help/Index.cshtml | 72 ----- .../Areas/VIM/Views/Help/Informations.xml | 21 -- .../Areas/VIM/Vim.Manifest.xml | 4 - .../Areas/VIM/Vim.Settings.json | 8 +- .../Controllers/MenuController.cs | 3 + Console/BExIS.Web.Shell/General.Settings.json | 167 +++++----- Console/BExIS.Web.Shell/Helpers/MenuHelper.cs | 31 ++ Console/BExIS.Web.Shell/Shell.Manifest.xml | 6 +- 45 files changed, 138 insertions(+), 1408 deletions(-) delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Views/Help/Information.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml diff --git a/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml b/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml index e4a12259e..e9568006b 100644 --- a/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml +++ b/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml @@ -595,5 +595,14 @@ + + + defaul menubar load with bar name like + menubarRoot + Accountbar + + + + diff --git a/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml b/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml index 81de70cef..1e255aafa 100644 --- a/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml @@ -27,10 +27,7 @@ title="Get partyTypes for account" description="Get partyTypes for account which are defined in setting.xml" icon="" controller="PartyService" action="GetPartyTypesForAccount" extends="" /> - + -

 

-

2. Manage Parties

-

 

-

- Through Manage Parties, you can see all the available entities, create, edit and delete them. - The red warning icon in action-required column shows that this party needs some relationships to be valid. -

-
-

Manage_Parties_img 

-

 

-

2.1. Create and Edit

-

 

-

- After clicking on Create Party in Manage Parties in the first step, you should select party type and its date range. Click on Next you will navigate to the next step.
- Here depends on the selected party type you will see some additional attributes. You have to fill the required fields.
- To edit later a party you will navigate to this page again. You will able to change all the fields except party type. -
-

create_party_1_img

-

 

-

2.2. Manage Relationship

-

- Every party could have some relationships with the other parties. If you do not define relationships, the party will save but it is not valid. You can add relationship later as well.
- Party relationships tab in the edit, or create party is to manage these relationships.
- To create a new relationship, click on create and you see the following window. Here you see all the available party relationship types depend on the definitions, which we already defined. The numbers in parentheses show the number of current relationships and the maximum relationships that this party to this relationship type can have.
- Clicking on one of them, you see some more options and available parties to make a relationship.
-

- - - -
-

new_party_relation_img 

-
-

Selecting a party, it asks you to enter some information and by default, it fills some of the fields. The title here is the title of the relationship. Start and end dates are important and will set the duration of the relationship. This duration should fit the duration of a source party and the target party; otherwise, you will face an error.

-

new_party_relation2_img 

-

- Click on the edit icon on the last column of each relationship make you able to edit the relationship.
- Click on the view icon make you able to see the detail of a relationship.
- Click on delete icon make you able to delete a relationship if the minimum cardinality of its relationship types preserved. -

-

 

-

3. Party creates while registration

-
-

A party type Person is created while registration. User guides to fill information fields needed for its party. - This page is available in tab "Additional attributes" during edit a party type Person.

-

 

-

registration_img 

- -

 

-

 

- - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml deleted file mode 100644 index e5865b3c5..000000000 --- a/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - On this page you are able to ...
- - - - - - - This guide will walk you through the ... - - - - \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj index 77f3c7189..1982fd36e 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj @@ -66,7 +66,6 @@ - @@ -408,7 +407,6 @@ - @@ -417,7 +415,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs deleted file mode 100644 index 68e5bcd46..000000000 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs +++ /dev/null @@ -1,19 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Dcm.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /DDM/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("DCM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml index 0a6354124..d16105719 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml @@ -30,11 +30,6 @@ controller="Push" action="index" extends="./menubarRoot/collect" />--> - - -

Data Collection ToC

-
-

1. Overview -

2. Create Dataset -

   2.1. Copy an existing Dataset -

   2.2. Content -

   2.3. Messages -

3. Upload Data -

   3.1. Upload Tabular Data - -

   3.2. Upload File -

4. Import Data - -

5. Push Big File -

6. Manage Metadata Structure - - -} - - - -

1. Overview

-

 

-

The Data Collection Module provides tools to create new datasets, enter metadata, upload data to the system, and import metadata structures (i.e. schemas). There are some workflows available under the Collect tab and also in the Setup:

-
    -
  • Create Dataset
    • -
  • Upload Data
    • -
  • Import Data
    • -
  • Push Big File
    • -
  • Manage Metadata Structure
    • - -
-

 

-

2. Create Dataset

-

 

-

This wizard will assist you in creating a new dataset in BEXIS2. The Wizard is very flexible and builds up differently depending on the selected Metadata structure. Therefore, we describe only the basic functions here.

-

The first step is to generate an empty or a copy of an existing dataset based on your selection of the two mandatory elements: Data Structure, and Metadata Structure.

-

Create Dataset 

-

The next stage is determined by the selected metadata structure.

-

 

-

2.1. Copy an existing Dataset

-

By choosing an existing Dataset instead of creating a new one, you are able to make a copy of that dataset. Related to the Dataset, you can choose a Data Structure, but there is only one related Metadata Structure for each dataset.

-

You are able to use predefined content or change fields as you want.

- -

 

-

2.2. Content

-

The content area is where you enter metadata describing your dataset. The forms provided here may look different and contain different attributes depending on the metadata schema (structure) you have chosen in the first step.

-

 

-

Required           Required attributes

-

Add        Add an attribute

-

Mines        Remove an attribute

-

Up Down  Change order of the attribute

-

ExpandCollapse      Expand / collapse

-

 

-

On the bottom of the page, there is a button titled Validate to examine whether required attributes have been filled and whether the information complies with the business logic. The validation may also be triggered by clicking on the Submit button.

-

You could edit a submitted dataset or make a copy of that by clicking on the Edit or Copy buttons.

- -

When an input is faulty, the input field is highlighted in red. If you go with the mouse over the box, you get information about what is wrong.

- - -

2.3. Messages

-

The content area is where you enter metadata describing your dataset. The forms provided here may look different and contain different attributes depending on the metadata schema (structure) you have chosen in the first step.

- -

messages

- -

 

-

3. Upload Data

-

 

-

To upload your data, please go to the Collect > Upload Data via main menu. This wizard will assist you in uploading data into the BEXIS2 repository. A dataset can be structured or unstructured (i.e tabular or file).

-

 

-

Upload Data 

-

 

-

3.1. Upload Tabular Data

-

The term "Tabular data" is used for all datasets where there internal structure of the data is "known" to the system. For example, in a data table the header, which defines the columns (i.e. variables) is the structure of the data. Before uploading/importing data to the system the data structure needs to be created through the Data Structure Manager.

-

Uploading a tabular data follows the following steps.

-

 

- -

Select File

-

- In the first step an existing file containing your data needs to be selected. You can either select a file from your local computer or a file that has been uploaded to the server prior to starting the Upload Wizard. - The second option is designed for files larger than 4 MB that may take several minutes to transfer. The wizard supports file formats of Microsoft Excel or ASCII. - Microsoft Excel files are required to use a template created while creating a Data Structure (refer to Data Planning User Guide for more details). - Once a file has been successfully selected, click the Next button and proceed to the next step. -

-

Upload_Tabular 

-

 

- - - -

Get File Information

-

- For all Microsoft Excel files using a BEXIS2 template the file information and data structure is automatically extracted and this step is omitted. Please refer to the Data Planning User Guide for more details on how to create such a template. -

-

- For all other Excel files, users need to provide the information by selection the data on the screen. -

-

Upload_Tabular 

- -

- For all ASCII files users need to provide information on the file structure and formatting. -

-

First, please choose a separator that is being used to separate data values from each other in your ASCII file.

-

Depending on your language different punctuation is used for decimal values. Please choose the one present in your ASCII file.

-

Next please specify whether the orientation of your data is column-wise or row-wise (see figure below).

- -

Datasets may contain empty rows or columns on top or to the left before the header and the actual data values start. Please specify this offset in number of columns or rows. 

-

Further, your data file may contain a header defining variable names, types etc. The row/column where this header starts needs to be specified (see figure below).

-

Offset.JPGVariables.JPG 

-

Finally, the row/column where the actual data values start needs to be specified.

-

 

-

Specify Dataset

-

In BEXIS2 your data is stored and managed as part of a dataset. A dataset may contain one or more of your data files. But all data files within one dataset must be of the same data structure, i.e. the number of variables and their properties must be identical in each file. To upload your data to the system, please select one existing dataset from the dropdown list.

- - -

Choose Update Method

-

While adding data to an existing dataset you need to specify how you want to update.

-

- By Update the user need to specify a unique identifier (e.g. primary key) for each tuple (i.e. row) in your dataset. If your dataset already contains a variable with such a key, please select it. Otherwise, a primary key can be created by combining available variables. Please click the Check button to verify whether the selected combination is unique. If you go back and change something in the process of uploading, you need to check the primary key again. -

-

Choose Update Method 

-

By Append, the lines are uploaded directly to the data without checking for duplication.

-

 

-

Validation

-

With this step, the selected data file is validated against the selected data structure. Both, the structure of the data (e.g. variable properties) and whether the data values fit to the specified structure (e.g. data type, value range) is evaluated.

-

Click on Validate button to validate the data file.

-

If you go back and change something in the process of uploading, you need to validate the file again.

- -

Summary

-

With this final step a summary of your uploaded data file is provided. Please check the information and click the Finish button to confirm and finalize the upload.

-

 

-

3.2. Upload File

-

An unstructured data could be either selected from your local computer or could be a file that has been uploaded to the server. In the case of unstructured data, we do not read the contents of the data. We copy the files to the server and place them in relation to the dataset.

-

BEXIS2 application can support many file formats which are referred on the relevant page.

-

The Maximum acceptable file size up to now is: 1024 MB.

-

Select File

-

 

- -

4. Import Data

-

The Import Data wizard enables you to import both a tabular data structure and data in a single workflow. Import a file follows the following steps.

-

 

- -

Select File

-

In the first step an existing file containing both your data and the names of the variables needs to be selected. You can either select a file from your local computer or a file that has been uploaded to the server prior to starting the Upload Wizard. The second option is designed for files larger than 4 MB that may take several minutes to transfer. The wizard supports file formats of Microsoft Excel (*.xlsm, *.xlsx). Once a file has been successfully selected, click the Next button to proceed to the next step.

-

 

-

Select File

-

 

- -

Metadata

-

This step allows you to select the metadata schema that you would like to use for the dataset. There is no need to enter any metadata yet - after the last step you will be redirected to a page that allows you to enter the metadata. You can, however, change the title of the dataset. If you don't wish to change it, it will default to the name of the file you are using. Once you have selected a schema, click the Next button to proceed to the next step.

-

 

-

Metadata Schema

-

 

- -

Select Areas

-

You will see a table that represents the file that you selected during the first step. Here you can select, which part of the file should be used as variables and which parts should be interpreted as data.

-

For the variables, select a row or one part of a row and click the "Header" button. The selected area should now be highlighted in red. If you are using a BEXIS2 template file there is no need to select the whole header with unit, datatype, etc. Just select the names of the variables.

-

For the data, you can select multiple rows and click the "Data" button. The selected area should now be highlighted in blue. Please make sure that the data area contains as many columns as the header area. You can skip one or more rows by selecting the area above them, mark it as data, and then select the area below them and mark it as well. You can use the "Expand Selection" button to expand the last data area you selected to the last row of the file. This can be very helpful when working with large datasets.

-

If you made any mistakes during the selection process just use the "Reset" button to remove all markings and start over.

-

If you wish to upload data from a different worksheet you can select it from the dropdown-menu and click the "Change Worksheet" button. Please be aware that you can only upload data from one sheet at a time. Once you have selected the header and at least one data area, click the Next Button to proceed to the next step.

-

 

-

Select Areas

-

 

-

The representation of the data you will see in the table might differ from what you see in Microsoft Excel or similar programs.

-

Don't worry, your data will be uploaded correctly if you choose the correct datatypes during the next step.

-The following differences are known: -
    -
  • Dates and times
    • -
      -
    • Microsoft Excel users: Dates and times will be displayed as full timestamps, containing both a time and a date.
      • -
    • Libre Office users: Dates and times will be displayed as real numbers.
      • -
    -
  • Boolean values
    • -
      -
    • Libre Office users: Boolean values might be displayed as "0" and "1".
      • -
    -
  • Real Numbers
    • -
      -
    • Real numbers might be displayed with scientific notation.
      • -
    -
- - -

 

-

Verification

-

With this step you can define which units and datatypes your variables are using. The first column of dropdown-menus provides suggestions for attributes that are being used in other datasets and are similar to your variables. If you select one of the suggestions, unit and datatype are automatically adjusted. If you don't wish to use the suggestions, feel free to choose unit and datatype yourself.

-

The "Validate" button allows you to check if the datatypes you selected are suitable for the data you selected in the previous step. This allows you to recognize errors early and correct your selection. Once you've selected your units and datatypes, click the Next button to proceed.

-

 

-

Verification

-

 

- -

Summary

-

The summary step provides an overview of the dataset that is about to be created. When you click the Finish button, datastructure and dataset will be created and the data will be added. This might take a while, depending of the size of your file.

-

Upload_Tabular_1

-

As soon as this process is finished, you will be redirected to your new dataset and can add metadata, view primary data and datastructure, set permissions or publish the dataset.

- -

 

-

5. Push Big File

-

 

-

Each user has a personal folder on the server where files are stored temporary. On this page you can see the uploaded files. You can delete each file by clicking on the X, or use these files later, when you want to upload data to a dataset.

-

Push Big File

-

 

-

6. Manage Metadata Structure

-

 

-

Metadata structures (also called schemas or profiles) are typically created and imported by a data manager or administrator of the system. Thus this import function is available under the Setup > Import metadata Structure. The wizard will assist you in importing your metadata structure into the BEXIS2. A metadata structure must be defined in a XSD schema file.

-

When importing a metadata schema into BEXIS2, each element of the XSD file(s) is analyzed for its type, name, annotations, attributes, data types, constraints etc. Based on this information a form is automatically being created. For example, if an element is of data type Date, a date picker UI component will be used in the form. Also all names and descriptions are used exactly as they are in the XSD file(s).

-

NOTE: There are metadata standards available for almost any domain or type of data. It is good practice to follow one of them in order to ensure interoperability later on. However, although technical possible, most standards are very complex and should not be used as a whole. Users would just be overwhelmed and may need only a small selection of elements to describe their data. Standards are designed to cover a great range of use cases and data managers (in collaboration with their community) should make the effort in defining a set of feasible metadata elements in a profile (XSD file).

-

IMPORTANT: Please check, whether the XSD schema files have any dependencies to other files. You can find the dependencies in the import or include tags.

-

Metadata1

-

The current BEXIS2 system requires all referenced files to be locally available on the server (no URL to external resource). So you may need to store all references first to a local folder, change the schema location path in every file (e.g. ./fileName.xsd) and then upload all files to the server. (See section Push Big File).

-

metadata2

-

metadata3 

-

 

-Upload a Metadata Structure follows the following steps: -

 

- -

Select File

-

In the first step an existing file containing your data needs to be selected. You can either select a XSD file from your local computer or a file that has been uploaded to the server prior to starting the Wizard. You may use the "Push big data to server" function in the Collect menu to upload multiple related XSD files.

-

Note: Please upload a valid XSD structure. BEXIS2 does not check this kind of validation.

-

 

-

Select XSD File 

-

 

- -

Read Source

-

Please specify a name (i.e. display name) for the new metadata structure. You may also enter a root node if only a part of the XSD is to be used (optional).

-

Read XSD File

To find the root node open the XSD Schema file and have a look on the element tags. In the example of ABCD it looks like this.

-

img27

If no root node is selected then the wizard will automatically select the first element which is a complex type. But it is also possible to define the element "DataSet" as root node and the metadata structure starts from this element. The Name of a metadata structure must be unique and the root node must exist.

-

 

- -

Set Parameters

-

For the system to handle a dataset at least the title and a description is needed. In this step these two elements, which are typically available in all metadata structures, should be identified and made explicit to the system.

-

Set XSD Parameters 

-

 

- -

Summary

-

 

-

The Summary page is an overview about the created metadata structure.

-

Summary

-

 

-

 

-

 

- Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml deleted file mode 100644 index 13c4c2180..000000000 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - - This wizard will assist you in creating a new dataset. Please select a data structure and a metadata structure below. - Or select a dataset as template to use the metadata structure and the metadata from the selected dataset. - - - - - - -

This guide will walk you through the basics of data collection including how to upload data and how to import a metadata structure.

- - - - - - - This wizard will assist you in adding a new metadata structure (i.e. schema) to the system. A metadata structure must be defined in XSD schema files. - Since XSD files can be defined in various ways this wizard is build on a few assumptions (e.g. with dependencies). Please consult the Help for more details. - - - - - - - Each user has a personal folder on the server where files are stored temporary. This wizard will assist you in pushing your files to server. You can also see the uploaded files, delete each file, or use these files later, when you want to upload data to a dataset. - - - - - - - This wizard will assist you in uploading data files to the system and adding them to a dataset. - - - - \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj index d6f4d92c6..38802468d 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj @@ -150,7 +150,6 @@ - @@ -215,7 +214,6 @@ - @@ -230,7 +228,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs deleted file mode 100644 index 567eb65eb..000000000 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,20 +0,0 @@ -using BExIS.Utils.Config; -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Ddm.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /ddm/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("DDM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml index c6b830ad5..c92ff3826 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml @@ -32,11 +32,6 @@ controller="dashboard" action="index" extends="./menubarRoot" /> - - - -

img1 

- - - -

 

- -

3.1. Mapping Overview

-Mapping tool is accessible through the Manage Metadata Structure by clicking on the arrow buttons. Mapping could be defined to or from the system. -

The page of Metadata Structure Mapping is divided into 3 sections. The source is displayed on the left and the target on the right side. All created mappings are displayed in the middle.

-

img1 

-

 

-

- Source and target in the left and right side includes two parts: Simple and Complex blocks. First name, last name or full name of a person are examples of Simple elements. A Complex element could be a person. - Search box is provided for each side (source or target) seperatly. -

- -

Mappings are connections between the source and the target. There are different connection possibilities between the simple attributes. Generally only the connection between two simple attributes is considered.

-

With the aid of a transformation rule, it is possible to cover a wide range of different cases. A transformation rule consists of a RegEx and a mask. With an example you can check the values and the expected result.

- - -

3.2 Mapping Examples

-

Following is some examples of one to one, one to many and many to one mapping.

- -Example: One to One -

This example creates a connection between two titles. All words are separated by a RegEx and then arranged differently via the mask.

-

img1 

-EXAMPLE: One to Many -

This example creates a connection between a name in one side and the FirstName and the LastName in other side. In the transformation rule, the first and last names are separated from one another by a RegEx and then positioned in the mask via the variable.

-

img1 

-EXAMPLE: Many to One -

This example creates a connection between the FirstName and LastName by a name. Here is no RegEx needed but the mask ordered from both variables.

-

img1

- -

3.3. Create a mapping

-
    -
  1. Choose a simple or complex element from the source.
    2. -
  2. Add Element to the middle section by clicking the orange arrow next to the element.
    3. -
  3. Choose a simple or complex element from the target.
    4. -
  4. Create the mapping by clicking on the create button
    5. -
  5. All available simple elements are listed in the mapping container for this mapping. Draw a line by clicking on one simple element from the source side and drag it to a simple element on the target side.
    6. -
  6. If needed, add RegEx and mask to the transformation rule.
    7. -
  7. Press on the save button after entering values in the blocks.
    8. -
- -

3.4. Key overview

-

key_overview

- -

4. Publishing a Dataset Version

-

Prepare the data is from now available for two brokers and a three data repositories.

-
    -
  • - Brokers: -
      -
    • GFBIO
      • -
    • Pensoft
      • -
    -
    • -
  • - Data Repositories: -
      -
    • GFBIO Collections
      • -
    • Pangaea
      • -
    • Pensoft
      • -
    -
    • -
- -

- There is limitation to publish a dataset version:
- First of all preparing dataset versions is only possible if the metadata is valid.
- Second is related to the Pensoft. All data prepared for Pensoft must be generated with the GBIF metadata structure. -

- -

4.1. Publish

-

Publish a dataset is attainable through the Publish tab on the dataset view.

-

All available data center are listed in a dropdown. After selcting a data center, system tries to convert the data and the metadata as defined in the submissionConfig.xml. If something fails a warning message will displayed.

-

 

-

There are two types of fails:

-
    -
  1. The system is not able to convert the data.
    2. -
  2. Metadata is not valid. In this case you can continue the procedure but the metadata.xml is not valid against the exported xsd schema.
    3. -
-

img3 

-

 

-

4.2. GFBIO

-

Via the GFBIO portal you can start a submission and publish your dataset. Depending on the subject of the data set, a suitable Data Repository is defined. There are different main Types:

-
    -
  • Pangaea
    • -
  • Collections
    • -
  • ENA
    • -
-

Each data repository has different data requirements. BEXIS2 offers an export for Pangea and Collections.

- - -

The data for the collections is stored in a zip file includes

-
    -
  1. Schema - XSD Schema for the metadata
    2. -
  2. Data.*** - Primary Data
    3. -
  3. Data structure - Structure of the primary data
    4. -
  4. Manifest File - General informations about the Dataset
    5. -
  5. Metadata - Metadata informations about the dataset
    6. -
-

For the Pangea, the metadata and primary data are stored in a text file.

- - - -

 

-

 

- - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml deleted file mode 100644 index 59329e0e0..000000000 --- a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - On this page you are able to export metadata to a standard compliant XML file, i.e. ABCD or EML.
-
    -
  • Please select a metadata structure first (tab)
    • -
  • Select one or more datasets to export
    • -
  • Click the export button to create XML files
    • -
- - - - - - - This guide will walk you through the basics of using data dissemination. - - - - \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj index 6a9d59fbc..fe2604465 100644 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj @@ -123,7 +123,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs deleted file mode 100644 index 2cc6de42f..000000000 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,17 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Rpm.UI.Controllers -{ - public class HelpController : Controller - { - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("RPM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml index 89055e887..76008d0c3 100644 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml @@ -11,11 +11,6 @@ - - - @@ -205,11 +204,9 @@ - - diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs deleted file mode 100644 index bbaf22efb..000000000 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,16 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Sam.UI.Controllers -{ - public class HelpController : Controller - { - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("SAM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml index 3891160b8..fb30f940d 100644 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml @@ -59,10 +59,6 @@ controller="Files" action="FileList" argument="Files list" extends="./settingsRoot" />--> - -
-

Administration ToC

-
-

1. Overview -

2. Registration -

   2.1. Login -

3. Users -

   3.1. Create a user -

   3.2. Edit a user -

4. Groups -

   4.1. Create a group -

   4.2. Edit a group -

5. Permissions -

   5.1. Feature Permissions -

   5.2. Datasets Permissions -

6. Manage Datasets -

7. API Token - -} - - - -

1. Overview

- -

- By default, only a few components of BEXIS2 are accessible for anonymous users. Any further access to the application is available for authorized users, only. Therefore, Administration module provides probably of user registration that could control by administrators. After a successful registration, user is able to logon to BEXIS2 using its account credentials for authentication.
- Features. The set of features is fixed and corresponds to the different hierarchical items of the menu bar.
- Permissions. Within the system, it is possible to add, remove or modify existing permissions on features and datasets. -

-

 

-

2. Registration

-

- Registration is accessible through the menu bar. All fields are mandatory and system needs accept of the Terms and Conditions. - To complete successfully the registration process you need to react to a confirmation Email. -

-

registration

-

 

-

2.1. Login

-

First, press Login button. The system redirects you to the login form and you have to enter your account credentials (username and password). If the login is successful, you will see Dashboard. Otherwise, the system will notify you about the status and reason why the logon was not successful.

-

login

-

 

-

3. Users

-

Caution! This part of the system is secured. You may not have access to it.

-

BEXIS2 provides different features for managing users. These are typically available to system administrators only. Each of them is described in more detail in one of the following subsections.

-

users

-

3.1. Create a user

-

In addition to the self-registration procedure, user accounts may also be created by an administrator. This feature is available from Setup > Manage Users. Please press the Create button. A modal window will pop up that contains the user creation form. Similar to the self-registration, the system supports you with validation on all information entered.

-

create_user

-

 

-

3.2. Edit a user

-

Within BEXIS2 you are able to display and modify user information. For security and usability reasons, the system allows modification only for certain parts of the user information. Please go to Setup > Manage Users and press the Edit button of the respective user. You are now able to alter the user information. Changes are committed to the system when you press the Save button.

-

For any given user memberships to certain groups need to be specified via the tab Membership.

-

You can change the status easily by (un)select the corresponding checkbox.

-

edit_user

-

 

-

4. Groups

-

Caution! This part of the system is secured. You may not have access to it.

-

BEXIS2 provides different features for the managing groups. They are typically available to system administrators only. Each of them is described in more detail in the following subsections.

-

groups 

-

4.1. Create a group

-

This feature is available from Setup > Manage Groups. Please press the Create button. A modal window will pop up that contains the group creation form. The system supports you with validation on all information entered.

-

create_group 

-

 

-

4.2. Edit a group

-

Within BEXIS2 you are able to display and modify group information. Please go to Setup > Manage Groups and press the Edit button of the respective group. You are now able to alter the group information. Changes are committed to the system once you pressed the Save button.

-

For any given user memberships to certain group need to be specified via the tab Membership.

-

You can change the status easily by (un)select the corresponding checkbox.

-

edit_group 

-

 

-

5. Permissions

-

Caution! This part of the system is secured. You may not have access to it.

-

Permission is a rule that contains certain security regulations. In general, it is possible to set a rule on both, users and groups.

-

The security system of BEXIS2 distinguishes between two types of permissions. On the one hand, there are feature permissions, which allow or prohibit the access to well-defined and delimited areas of the application. This type of permissions is working on functional objects (e.g. actions that should be performed) - so called Features. On the other hand, data permissions provide the ability to protect real data (e.g. datasets, research plans and so on).

-

 

-

5.1. Feature Permissions

-

To be able to modify features, Please go to Setup > Manage Feature Permissions. This will bring up a page with a tree on the left side.

-

Selecting a checkbox in the navigation tree (e.g. Search) will make that feature accessible without authentication (public access). Please use with care!

-

By clicking a feature name (a node in the tree), the system will show a table on the right side (see below). This table contains all subjects (users and groups) and their feature permission status. You may grant or deny permissions for individual users or groups using the radio buttons. If a permission is not explicitly set (i.e None) permissions are inherited from up level features. Inherited permissions are shown in the first column as effective permissions.

-

features 

-

 

-

5.2. Entity Permissions

-

The security system of BEXIS2 is working on both, functional (features) and non-functional (entities) items. Please go to Setup > Manage Entity Permissions if you like to manage access to entities (datasets).

-

By selecting a dataset (i.e. a row in the table), the system will show a second table underneath the first one, which contains all subjects (users and groups) and their different data permission statuses regarding the selected dataset. On this page, you are also able to alter the different kinds of data permissions for a selected dataset.

-

Selecting the checkbox in the first column (i.e. IsPublic) will allow public access to that dataset without any authentication.

-

 

-

datasets 

-

 

-

In general, the system works on six different data permission types:

-
  • Read: allow/deny read & download access to primary data
    • -
  • Update: allow/deny manipulation (upload and update) of primary data
    • -
  • Delete: allow/deny deletion of the whole dataset
    • -
  • Grant: allow/deny to give permission to other users or groups
    • -

     

    -

    6. Manage Datasets

    -

    Via menu in Setup > Manage Datasets you are able to see a list of Datasets.

    -

    In this list you can see the status of each dataset and some useful actions for the maintenance of a dataset.

    -

    maintenance 

    -

    There are two ways to delete a dataset:

    -

    Delete: this function tags a dataset to exclude it from nearly all features of the system (e.g. search). But the dataset itself will stay inside the database. So later on you are able to recover the dataset - if needed.

    -

    Purge: the dataset will be removed from the system at all (incl. removal of data permissions, metadata and primary data). There is no way to rollback that action.

    -

    Note that if you purge a dataset, you cannot recover it at all.

    -

     

    -

    7. API Token

    -

    - In general, the APIs of BEXIS2 are protected by both mechanisms, authentication and authorization. In contrast to the login where usual credential are used, the APIs are using a personalized token for authentication. Within the user menu, each user has the possibility to show her/his own token. Afterwards, that token can be used for the APIs. -

    -

    token 

    - -

     

    -

     

    - - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml deleted file mode 100644 index 381b48741..000000000 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,108 +0,0 @@ - - - - -

    In the case of any problems with authorization, please contact with your administrator.

    -     - -     - - -

    Through this interface you can login into the system.

    -

    If you have not a username, you need to register into the system first.

    -     - -     - - -

    This page summarizes your personal account information. Furthermore, you are able to edit that data, but there are two important facts you should be aware of:

    -
      -
    1. - Password Change - You need to enter both, Password and Confirm Password. -
      2. -
    2. - Security Question/Answer - You need to enter both, Security Question and Security Answer. -
      3. -
    -

    Otherwise, the abovementioned properties aren't changed.

    -     - -     - - - - Here you are able to manage how users (or groups) have access to individual datasets. - Please select a dataset in the table below and specify who should have permissions to Information, update, delete, download data, or who is able to grant access to other users (Note: metadata is always free). - Ticking the checkboxes "public access" in the upper table will make a dataset accessible without authentification (public access to primary data). Please use with care! - By default only the creator of a dataset (in the system) has full access, all other permissions are not set, which means access is denied. - Grants for individual users rule out higher level settings for groups. - Please note that any change will take effect immediately without further confirmation or save/submit action. - - - - - - - With this interface you are able to see a list of Datasets. In this list you can see the status of each dataset and some useful actions for the maintenance of a dataset. - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - - Here you are able to manage how users (or groups) have access to individual system features or entire modules. - Please click on the name in the tree structure on left to Information individual permissions. - Ticking the checkboxes in the navigation tree will make a feature accessible without authentification (public access). - Please use with care! - By default feature permissions are not set, which means access is denied unless access permissions are explicitly granted or inherited from an upper level feature (e.g. module). - Individual grants on features rule out higher level settings. Effective permissions are shown in the first column of the table. - Please note that any change will take effect immediately without further confirmation or save/submit action. - - - - - - - With this interface you are able to manage groups. New groups can be added with the "Create" button. Existing groups can be edited (properties, members, delete) using the "Edit" button. - - - - - - - This guide will walk you through the basics of using administration parts including how to registrate or log on, how to manage users or groups and how to manage permissions. - - - - - - - With this interface you are able to manage users. New users can be added with the "Create" button. Existing users can be edited (properties, memberships, delete) through the "Edit" button. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj b/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj index 9c716d380..9bc62da87 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj @@ -44,7 +44,6 @@ 4 - @@ -298,12 +297,10 @@ - Designer - Designer diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs deleted file mode 100644 index 54075edbb..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs +++ /dev/null @@ -1,19 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Vim.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /VIM/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("VIM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml b/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml deleted file mode 100644 index 6eb9d333e..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml +++ /dev/null @@ -1,72 +0,0 @@ -@section Information -{ - This guide will walk you through the basics of visualization. -} -@section leftPane{ -
    -

    Visualization ToC

    -
    -

    1. Overview -

    2. Select Ranges -

       2.1. Select category -

       2.2. Select Time -

       2.2. Time Slider -
    -} - - -

     

    -

     

    - -

    1. Overview

    -

    - Visualization or in other words the visual representation of data in an easily comprehensible form is the feature of the visualization module for BEXIS2. User of BEXIS2 is able to get a quick overview of the system behaviour with looking at diagrams. - Visualization is accessible through setup in the main menu.
    -

    -

     

    -

    all

    -

     

    -

    2. Select Ranges

    -

    - Visualization provides diagrams depend on the selected ranges in different dropdown lists. There is two different lists to control the diagram. - One is to select the kind of data and one is to select the time range.
    -

    -

    2.1. Select Category

    -

    - On the first view, when the selector shows "Select a category", you can see a histogram with data of created and deleted datasets. - The current version of the BEXIS2 makes you able to see the statistic of system activities, created datasets and deleted datasets over time.
    -

    -

    all

    - -

    2.2. Select Time

    -

    - In the drop-down list "Select time, you can find the past years. By default, the chart displays the data distribution over the entire time from the first activities.
    - Select a specific year and see the statistic for only that year, separated in twelve months.
    -

    -

    all

    - -

    2.3. Time Slider

    -

    - If you do not like to see all data behaviour from the first activity to the end, you can select a period by the help of the time slider..
    -

    -

    all

    - -

     

    -

     

    - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml deleted file mode 100644 index 59329e0e0..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - On this page you are able to export metadata to a standard compliant XML file, i.e. ABCD or EML.
    -
      -
    • Please select a metadata structure first (tab)
      • -
    • Select one or more datasets to export
      • -
    • Click the export button to create XML files
      • -
    -     - -     - - - - This guide will walk you through the basics of using data dissemination. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml index 978589de3..f4d877727 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml @@ -16,9 +16,5 @@ controller="visualization" action="index" extends="./settingsRoot" /> -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json index 6db207bee..8a33564f9 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json +++ b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json @@ -3,12 +3,6 @@ "name": "Visualization", "description": "stats about datasets", "entries": [ - { - "key": "help", - "title": "Help URL", - "value": "", - "type": "String", - "description": "URL to the manual. If empty, it links to the latest manual from BEXIS2" - } + ] } \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Controllers/MenuController.cs b/Console/BExIS.Web.Shell/Controllers/MenuController.cs index 7f85a43b2..c4b1620d0 100644 --- a/Console/BExIS.Web.Shell/Controllers/MenuController.cs +++ b/Console/BExIS.Web.Shell/Controllers/MenuController.cs @@ -3,6 +3,7 @@ using BExIS.UI.Models; using BExIS.Web.Shell.Helpers; using System; +using System.Linq; using System.Web; using System.Web.Mvc; using Vaiona.Web.Extensions; @@ -56,6 +57,8 @@ public JsonResult Index() menu.LaunchBar = MenuHelper.MenuBar("lunchbarRoot"); menu.MenuBar = MenuHelper.MenuBarSecured("menubarRoot", userName); menu.Settings = MenuHelper.MenuBarSecured("settingsRoot", userName, true); + MenuHelper.AdditionalHelpBar(menu.LaunchBar.FirstOrDefault(i =>i.Title.Equals("Help"))); + menu.AccountBar = MenuHelper.AccountBar(isAuthenticated, userName); diff --git a/Console/BExIS.Web.Shell/General.Settings.json b/Console/BExIS.Web.Shell/General.Settings.json index fe81621b6..f20526dc6 100644 --- a/Console/BExIS.Web.Shell/General.Settings.json +++ b/Console/BExIS.Web.Shell/General.Settings.json @@ -103,82 +103,97 @@ "description": "send or excluded exception sending via email." }, { - "key": "landingPage", - "title": "Landing Page (without login)", - "value": "ddm, publicsearch, index", - "type": "String", - "description": "User is not logging in -> app goes to e.g. (ddm, publicsearch, index). If no destination is entered, the landingpage.htm is loaded from the tenant/content/landingpage.htm" - }, - { - "key": "showMenuOnLandingPage", - "title": "Show menu on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide menu on your own created landing page" - }, - { - "key": "showHeaderOnLandingPage", - "title": "Show header on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide header on your own created landing page" - }, - { - "key": "showFooterOnLandingPage", - "title": "Show footer on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide footer on your own created landing page" - }, - { - "key": "landingPageForUsers", - "title": "Landing Page after login for users with permission", - "value": "ddm, search, index", - "type": "String", - "description": "User logged in, but does not have permission to view the page; shell, home, nopermission is by default; Alternatives must be in a module NOT shell" - }, - { - "key": "landingPageForUsersNoPermission", - "title": "Landing Page after login for users with no permission", - "value": "shell, home, nopermission", - "type": "String", - "description": "Landing page for users, after logging in successfully without permission." - }, - { - "key": "systemEmail", - "title": "System E-Mail Address", - "value": "david.schoene@uni-jena.de", - "type": "String", - "description": "All administrative information will be sent to this email." - }, - { - "key": "usePersonEmailAttributeName", - "title": "Use Person E-Mail Attribute Name", - "value": false, - "type": "Boolean", - "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." - }, - { - "key": "personEmailAttributeName", - "title": "Person E-Mail Attribute Name", - "value": "Email", - "type": "String", - "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." - }, - { - "key": "useMultimediaModule", - "title": "Use Multimedia Module?", - "value": true, - "type": "Boolean", - "description": "This flag turns on/off the Multimedia Module." - }, - { - "key": "faq", - "title": "FAQ", - "value": "https://github.com/BEXIS2/Core/wiki/FAQ", - "type": "String", - "description": "FAQ URL. Can link to an external page." - } + "description": "...", + "key": "help", + "title": "Addition Help Links", + "type": "EntryList", + "value": [ + { + "description": "FAQ", + "key": "helpLink", + "title": "Url", + "type": "String", + "value": "https://github.com/BEXIS2/Core/wiki/FAQ" + } + ] + }, + { + "key": "landingPage", + "title": "Landing Page (without login)", + "value": "ddm, publicsearch, index", + "type": "String", + "description": "User is not logging in -> app goes to e.g. (ddm, publicsearch, index). If no destination is entered, the landingpage.htm is loaded from the tenant/content/landingpage.htm" + }, + { + "key": "showMenuOnLandingPage", + "title": "Show menu on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide menu on your own created landing page" + }, + { + "key": "showHeaderOnLandingPage", + "title": "Show header on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide header on your own created landing page" + }, + { + "key": "showFooterOnLandingPage", + "title": "Show footer on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide footer on your own created landing page" + }, + { + "key": "landingPageForUsers", + "title": "Landing Page after login for users with permission", + "value": "ddm, search, index", + "type": "String", + "description": "User logged in, but does not have permission to view the page; shell, home, nopermission is by default; Alternatives must be in a module NOT shell" + }, + { + "key": "landingPageForUsersNoPermission", + "title": "Landing Page after login for users with no permission", + "value": "shell, home, nopermission", + "type": "String", + "description": "Landing page for users, after logging in successfully without permission." + }, + { + "key": "systemEmail", + "title": "System E-Mail Address", + "value": "david.schoene@uni-jena.de", + "type": "String", + "description": "All administrative information will be sent to this email." + }, + { + "key": "usePersonEmailAttributeName", + "title": "Use Person E-Mail Attribute Name", + "value": false, + "type": "Boolean", + "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." + }, + { + "key": "personEmailAttributeName", + "title": "Person E-Mail Attribute Name", + "value": "Email", + "type": "String", + "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." + }, + { + "key": "useMultimediaModule", + "title": "Use Multimedia Module?", + "value": true, + "type": "Boolean", + "description": "This flag turns on/off the Multimedia Module." + }, + { + "key": "faq", + "title": "FAQ", + "value": "https://github.com/BEXIS2/Core/wiki/FAQ", + "type": "String", + "description": "FAQ URL. Can link to an external page." + } ] } diff --git a/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs b/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs index cc05617c4..0baac5ec1 100644 --- a/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs +++ b/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs @@ -2,6 +2,7 @@ using BExIS.Security.Services.Authorization; using BExIS.Security.Services.Objects; using BExIS.UI.Models; +using BExIS.Utils.Config; using System; using System.Collections.Generic; using System.Linq; @@ -215,6 +216,36 @@ public static List ExtendedMenu(XElement list) return menuItems; } + /// + /// defaul menubar load with bar name like + /// menubarRoot + /// Accountbar + /// + /// + /// + public static List AdditionalHelpBar(MenuItem help) + { + List menuItems = help.Items; + + var help_list = GeneralSettings.GetValueByKey("help") as List; + + // go throw each item + foreach (var link in help_list) + { + if (link != null) + { + MenuItem menuItem = new MenuItem(); + //get title of the item + menuItem.Title = link.Description; + menuItem.Url = link.Value; + + menuItems.Add(menuItem); + } + } + + return menuItems; + } + private static string getUrl(XElement element) { StringBuilder sb = new StringBuilder(); diff --git a/Console/BExIS.Web.Shell/Shell.Manifest.xml b/Console/BExIS.Web.Shell/Shell.Manifest.xml index eb531a1a3..a2c9510bd 100644 --- a/Console/BExIS.Web.Shell/Shell.Manifest.xml +++ b/Console/BExIS.Web.Shell/Shell.Manifest.xml @@ -36,11 +36,7 @@ extends="." /> - - + Date: Fri, 30 Jan 2026 12:37:54 +0100 Subject: [PATCH 11/29] Merge branch 'rc' of https://github.com/BEXIS2/Core into rc --- .../App_Data/BExIS.Web.Shell.xml | 9 + .../Areas/BAM/BAM.Manifest.xml | 5 +- .../Areas/BAM/BExIS.Modules.Bam.UI.csproj | 3 - .../Areas/BAM/Bam.Settings.json | 7 - .../Areas/BAM/Controllers/HelpController.cs | 19 -- .../Areas/BAM/Views/Help/Index.cshtml | 98 ------ .../Areas/BAM/Views/Help/Informations.xml | 16 - .../BExIS.Modules.Dcm.UI.csproj | 3 - .../Controllers/Legacy/HelpController.cs | 19 -- .../DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml | 5 - .../BExIS.Modules.Dcm.UI/Dcm.Settings.json | 8 +- .../Views/Help/Index.cshtml | 290 ------------------ .../Views/Help/Informations.xml | 39 --- .../BExIS.Modules.Ddm.UI.csproj | 3 - .../Controllers/HelpController.cs | 20 -- .../DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml | 5 - .../BExIS.Modules.Ddm.UI/Ddm.Settings.json | 7 - .../Views/Help/Index.cshtml | 13 - .../Views/Help/Information.xml | 81 ----- .../BExIS.Modules.Dim.UI.csproj | 3 - .../Controllers/HelpController.cs | 19 -- .../DIM/BExIS.Modules.Dim.UI/Dim.Manifest.xml | 4 - .../BExIS.Modules.Dim.UI/Dim.Settings.json | 7 - .../Views/Help/Index.cshtml | 197 ------------ .../Views/Help/Informations.xml | 21 -- .../src/routes/importjson/+page.svelte | 14 + .../BExIS.Modules.Rpm.UI.csproj | 1 - .../Controllers/HelpController.cs | 17 - .../RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml | 5 - .../BExIS.Modules.Rpm.UI/Rpm.Settings.json | 7 - .../BExIS.Modules.Sam.UI.csproj | 3 - .../Controllers/HelpController.cs | 16 - .../SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml | 4 - .../BExIS.Modules.Sam.UI/Sam.Settings.json | 7 - .../Views/Help/Index.cshtml | 143 --------- .../Views/Help/Informations.xml | 108 ------- .../Areas/VIM/BExIS.Modules.Vim.UI.csproj | 3 - .../Areas/VIM/Controllers/HelpController.cs | 19 -- .../Areas/VIM/Views/Help/Index.cshtml | 72 ----- .../Areas/VIM/Views/Help/Informations.xml | 21 -- .../Areas/VIM/Vim.Manifest.xml | 4 - .../Areas/VIM/Vim.Settings.json | 8 +- .../Controllers/MenuController.cs | 3 + Console/BExIS.Web.Shell/General.Settings.json | 167 +++++----- Console/BExIS.Web.Shell/Helpers/MenuHelper.cs | 31 ++ Console/BExIS.Web.Shell/Shell.Manifest.xml | 6 +- 46 files changed, 152 insertions(+), 1408 deletions(-) delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Views/Help/Information.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml delete mode 100644 Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml diff --git a/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml b/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml index e4a12259e..e9568006b 100644 --- a/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml +++ b/Console/BExIS.Web.Shell/App_Data/BExIS.Web.Shell.xml @@ -595,5 +595,14 @@ + + + defaul menubar load with bar name like + menubarRoot + Accountbar + + + + diff --git a/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml b/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml index 81de70cef..1e255aafa 100644 --- a/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/BAM/BAM.Manifest.xml @@ -27,10 +27,7 @@ title="Get partyTypes for account" description="Get partyTypes for account which are defined in setting.xml" icon="" controller="PartyService" action="GetPartyTypesForAccount" extends="" /> - + -

     

    -

    2. Manage Parties

    -

     

    -

    - Through Manage Parties, you can see all the available entities, create, edit and delete them. - The red warning icon in action-required column shows that this party needs some relationships to be valid. -

    -
    -

    Manage_Parties_img 

    -

     

    -

    2.1. Create and Edit

    -

     

    -

    - After clicking on Create Party in Manage Parties in the first step, you should select party type and its date range. Click on Next you will navigate to the next step.
    - Here depends on the selected party type you will see some additional attributes. You have to fill the required fields.
    - To edit later a party you will navigate to this page again. You will able to change all the fields except party type. -
    -

    create_party_1_img

    -

     

    -

    2.2. Manage Relationship

    -

    - Every party could have some relationships with the other parties. If you do not define relationships, the party will save but it is not valid. You can add relationship later as well.
    - Party relationships tab in the edit, or create party is to manage these relationships.
    - To create a new relationship, click on create and you see the following window. Here you see all the available party relationship types depend on the definitions, which we already defined. The numbers in parentheses show the number of current relationships and the maximum relationships that this party to this relationship type can have.
    - Clicking on one of them, you see some more options and available parties to make a relationship.
    -

    - - - -
    -

    new_party_relation_img 

    -
    -

    Selecting a party, it asks you to enter some information and by default, it fills some of the fields. The title here is the title of the relationship. Start and end dates are important and will set the duration of the relationship. This duration should fit the duration of a source party and the target party; otherwise, you will face an error.

    -

    new_party_relation2_img 

    -

    - Click on the edit icon on the last column of each relationship make you able to edit the relationship.
    - Click on the view icon make you able to see the detail of a relationship.
    - Click on delete icon make you able to delete a relationship if the minimum cardinality of its relationship types preserved. -

    -

     

    -

    3. Party creates while registration

    -
    -

    A party type Person is created while registration. User guides to fill information fields needed for its party. - This page is available in tab "Additional attributes" during edit a party type Person.

    -

     

    -

    registration_img 

    - -

     

    -

     

    - - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml deleted file mode 100644 index e5865b3c5..000000000 --- a/Console/BExIS.Web.Shell/Areas/BAM/Views/Help/Informations.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - On this page you are able to ...
    -     - -     - - - - This guide will walk you through the ... - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj index 77f3c7189..1982fd36e 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/BExIS.Modules.Dcm.UI.csproj @@ -66,7 +66,6 @@ - @@ -408,7 +407,6 @@ - @@ -417,7 +415,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs deleted file mode 100644 index 68e5bcd46..000000000 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Controllers/Legacy/HelpController.cs +++ /dev/null @@ -1,19 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Dcm.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /DDM/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("DCM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml index 0a6354124..d16105719 100644 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Dcm.Manifest.xml @@ -30,11 +30,6 @@ controller="Push" action="index" extends="./menubarRoot/collect" />--> - - -

    Data Collection ToC

    -
    -

    1. Overview -

    2. Create Dataset -

       2.1. Copy an existing Dataset -

       2.2. Content -

       2.3. Messages -

    3. Upload Data -

       3.1. Upload Tabular Data - -

       3.2. Upload File -

    4. Import Data - -

    5. Push Big File -

    6. Manage Metadata Structure - - -} - - - -

    1. Overview

    -

     

    -

    The Data Collection Module provides tools to create new datasets, enter metadata, upload data to the system, and import metadata structures (i.e. schemas). There are some workflows available under the Collect tab and also in the Setup:

    -
      -
    • Create Dataset
      • -
    • Upload Data
      • -
    • Import Data
      • -
    • Push Big File
      • -
    • Manage Metadata Structure
      • - -
    -

     

    -

    2. Create Dataset

    -

     

    -

    This wizard will assist you in creating a new dataset in BEXIS2. The Wizard is very flexible and builds up differently depending on the selected Metadata structure. Therefore, we describe only the basic functions here.

    -

    The first step is to generate an empty or a copy of an existing dataset based on your selection of the two mandatory elements: Data Structure, and Metadata Structure.

    -

    Create Dataset 

    -

    The next stage is determined by the selected metadata structure.

    -

     

    -

    2.1. Copy an existing Dataset

    -

    By choosing an existing Dataset instead of creating a new one, you are able to make a copy of that dataset. Related to the Dataset, you can choose a Data Structure, but there is only one related Metadata Structure for each dataset.

    -

    You are able to use predefined content or change fields as you want.

    - -

     

    -

    2.2. Content

    -

    The content area is where you enter metadata describing your dataset. The forms provided here may look different and contain different attributes depending on the metadata schema (structure) you have chosen in the first step.

    -

     

    -

    Required           Required attributes

    -

    Add        Add an attribute

    -

    Mines        Remove an attribute

    -

    Up Down  Change order of the attribute

    -

    ExpandCollapse      Expand / collapse

    -

     

    -

    On the bottom of the page, there is a button titled Validate to examine whether required attributes have been filled and whether the information complies with the business logic. The validation may also be triggered by clicking on the Submit button.

    -

    You could edit a submitted dataset or make a copy of that by clicking on the Edit or Copy buttons.

    - -

    When an input is faulty, the input field is highlighted in red. If you go with the mouse over the box, you get information about what is wrong.

    - - -

    2.3. Messages

    -

    The content area is where you enter metadata describing your dataset. The forms provided here may look different and contain different attributes depending on the metadata schema (structure) you have chosen in the first step.

    - -

    messages

    - -

     

    -

    3. Upload Data

    -

     

    -

    To upload your data, please go to the Collect > Upload Data via main menu. This wizard will assist you in uploading data into the BEXIS2 repository. A dataset can be structured or unstructured (i.e tabular or file).

    -

     

    -

    Upload Data 

    -

     

    -

    3.1. Upload Tabular Data

    -

    The term "Tabular data" is used for all datasets where there internal structure of the data is "known" to the system. For example, in a data table the header, which defines the columns (i.e. variables) is the structure of the data. Before uploading/importing data to the system the data structure needs to be created through the Data Structure Manager.

    -

    Uploading a tabular data follows the following steps.

    -

     

    - -

    Select File

    -

    - In the first step an existing file containing your data needs to be selected. You can either select a file from your local computer or a file that has been uploaded to the server prior to starting the Upload Wizard. - The second option is designed for files larger than 4 MB that may take several minutes to transfer. The wizard supports file formats of Microsoft Excel or ASCII. - Microsoft Excel files are required to use a template created while creating a Data Structure (refer to Data Planning User Guide for more details). - Once a file has been successfully selected, click the Next button and proceed to the next step. -

    -

    Upload_Tabular 

    -

     

    - - - -

    Get File Information

    -

    - For all Microsoft Excel files using a BEXIS2 template the file information and data structure is automatically extracted and this step is omitted. Please refer to the Data Planning User Guide for more details on how to create such a template. -

    -

    - For all other Excel files, users need to provide the information by selection the data on the screen. -

    -

    Upload_Tabular 

    - -

    - For all ASCII files users need to provide information on the file structure and formatting. -

    -

    First, please choose a separator that is being used to separate data values from each other in your ASCII file.

    -

    Depending on your language different punctuation is used for decimal values. Please choose the one present in your ASCII file.

    -

    Next please specify whether the orientation of your data is column-wise or row-wise (see figure below).

    - -

    Datasets may contain empty rows or columns on top or to the left before the header and the actual data values start. Please specify this offset in number of columns or rows. 

    -

    Further, your data file may contain a header defining variable names, types etc. The row/column where this header starts needs to be specified (see figure below).

    -

    Offset.JPGVariables.JPG 

    -

    Finally, the row/column where the actual data values start needs to be specified.

    -

     

    -

    Specify Dataset

    -

    In BEXIS2 your data is stored and managed as part of a dataset. A dataset may contain one or more of your data files. But all data files within one dataset must be of the same data structure, i.e. the number of variables and their properties must be identical in each file. To upload your data to the system, please select one existing dataset from the dropdown list.

    - - -

    Choose Update Method

    -

    While adding data to an existing dataset you need to specify how you want to update.

    -

    - By Update the user need to specify a unique identifier (e.g. primary key) for each tuple (i.e. row) in your dataset. If your dataset already contains a variable with such a key, please select it. Otherwise, a primary key can be created by combining available variables. Please click the Check button to verify whether the selected combination is unique. If you go back and change something in the process of uploading, you need to check the primary key again. -

    -

    Choose Update Method 

    -

    By Append, the lines are uploaded directly to the data without checking for duplication.

    -

     

    -

    Validation

    -

    With this step, the selected data file is validated against the selected data structure. Both, the structure of the data (e.g. variable properties) and whether the data values fit to the specified structure (e.g. data type, value range) is evaluated.

    -

    Click on Validate button to validate the data file.

    -

    If you go back and change something in the process of uploading, you need to validate the file again.

    - -

    Summary

    -

    With this final step a summary of your uploaded data file is provided. Please check the information and click the Finish button to confirm and finalize the upload.

    -

     

    -

    3.2. Upload File

    -

    An unstructured data could be either selected from your local computer or could be a file that has been uploaded to the server. In the case of unstructured data, we do not read the contents of the data. We copy the files to the server and place them in relation to the dataset.

    -

    BEXIS2 application can support many file formats which are referred on the relevant page.

    -

    The Maximum acceptable file size up to now is: 1024 MB.

    -

    Select File

    -

     

    - -

    4. Import Data

    -

    The Import Data wizard enables you to import both a tabular data structure and data in a single workflow. Import a file follows the following steps.

    -

     

    - -

    Select File

    -

    In the first step an existing file containing both your data and the names of the variables needs to be selected. You can either select a file from your local computer or a file that has been uploaded to the server prior to starting the Upload Wizard. The second option is designed for files larger than 4 MB that may take several minutes to transfer. The wizard supports file formats of Microsoft Excel (*.xlsm, *.xlsx). Once a file has been successfully selected, click the Next button to proceed to the next step.

    -

     

    -

    Select File

    -

     

    - -

    Metadata

    -

    This step allows you to select the metadata schema that you would like to use for the dataset. There is no need to enter any metadata yet - after the last step you will be redirected to a page that allows you to enter the metadata. You can, however, change the title of the dataset. If you don't wish to change it, it will default to the name of the file you are using. Once you have selected a schema, click the Next button to proceed to the next step.

    -

     

    -

    Metadata Schema

    -

     

    - -

    Select Areas

    -

    You will see a table that represents the file that you selected during the first step. Here you can select, which part of the file should be used as variables and which parts should be interpreted as data.

    -

    For the variables, select a row or one part of a row and click the "Header" button. The selected area should now be highlighted in red. If you are using a BEXIS2 template file there is no need to select the whole header with unit, datatype, etc. Just select the names of the variables.

    -

    For the data, you can select multiple rows and click the "Data" button. The selected area should now be highlighted in blue. Please make sure that the data area contains as many columns as the header area. You can skip one or more rows by selecting the area above them, mark it as data, and then select the area below them and mark it as well. You can use the "Expand Selection" button to expand the last data area you selected to the last row of the file. This can be very helpful when working with large datasets.

    -

    If you made any mistakes during the selection process just use the "Reset" button to remove all markings and start over.

    -

    If you wish to upload data from a different worksheet you can select it from the dropdown-menu and click the "Change Worksheet" button. Please be aware that you can only upload data from one sheet at a time. Once you have selected the header and at least one data area, click the Next Button to proceed to the next step.

    -

     

    -

    Select Areas

    -

     

    -

    The representation of the data you will see in the table might differ from what you see in Microsoft Excel or similar programs.

    -

    Don't worry, your data will be uploaded correctly if you choose the correct datatypes during the next step.

    -The following differences are known: -
      -
    • Dates and times
      • -
        -
      • Microsoft Excel users: Dates and times will be displayed as full timestamps, containing both a time and a date.
        • -
      • Libre Office users: Dates and times will be displayed as real numbers.
        • -
      -
    • Boolean values
      • -
        -
      • Libre Office users: Boolean values might be displayed as "0" and "1".
        • -
      -
    • Real Numbers
      • -
        -
      • Real numbers might be displayed with scientific notation.
        • -
      -
    - - -

     

    -

    Verification

    -

    With this step you can define which units and datatypes your variables are using. The first column of dropdown-menus provides suggestions for attributes that are being used in other datasets and are similar to your variables. If you select one of the suggestions, unit and datatype are automatically adjusted. If you don't wish to use the suggestions, feel free to choose unit and datatype yourself.

    -

    The "Validate" button allows you to check if the datatypes you selected are suitable for the data you selected in the previous step. This allows you to recognize errors early and correct your selection. Once you've selected your units and datatypes, click the Next button to proceed.

    -

     

    -

    Verification

    -

     

    - -

    Summary

    -

    The summary step provides an overview of the dataset that is about to be created. When you click the Finish button, datastructure and dataset will be created and the data will be added. This might take a while, depending of the size of your file.

    -

    Upload_Tabular_1

    -

    As soon as this process is finished, you will be redirected to your new dataset and can add metadata, view primary data and datastructure, set permissions or publish the dataset.

    - -

     

    -

    5. Push Big File

    -

     

    -

    Each user has a personal folder on the server where files are stored temporary. On this page you can see the uploaded files. You can delete each file by clicking on the X, or use these files later, when you want to upload data to a dataset.

    -

    Push Big File

    -

     

    -

    6. Manage Metadata Structure

    -

     

    -

    Metadata structures (also called schemas or profiles) are typically created and imported by a data manager or administrator of the system. Thus this import function is available under the Setup > Import metadata Structure. The wizard will assist you in importing your metadata structure into the BEXIS2. A metadata structure must be defined in a XSD schema file.

    -

    When importing a metadata schema into BEXIS2, each element of the XSD file(s) is analyzed for its type, name, annotations, attributes, data types, constraints etc. Based on this information a form is automatically being created. For example, if an element is of data type Date, a date picker UI component will be used in the form. Also all names and descriptions are used exactly as they are in the XSD file(s).

    -

    NOTE: There are metadata standards available for almost any domain or type of data. It is good practice to follow one of them in order to ensure interoperability later on. However, although technical possible, most standards are very complex and should not be used as a whole. Users would just be overwhelmed and may need only a small selection of elements to describe their data. Standards are designed to cover a great range of use cases and data managers (in collaboration with their community) should make the effort in defining a set of feasible metadata elements in a profile (XSD file).

    -

    IMPORTANT: Please check, whether the XSD schema files have any dependencies to other files. You can find the dependencies in the import or include tags.

    -

    Metadata1

    -

    The current BEXIS2 system requires all referenced files to be locally available on the server (no URL to external resource). So you may need to store all references first to a local folder, change the schema location path in every file (e.g. ./fileName.xsd) and then upload all files to the server. (See section Push Big File).

    -

    metadata2

    -

    metadata3 

    -

     

    -Upload a Metadata Structure follows the following steps: -

     

    - -

    Select File

    -

    In the first step an existing file containing your data needs to be selected. You can either select a XSD file from your local computer or a file that has been uploaded to the server prior to starting the Wizard. You may use the "Push big data to server" function in the Collect menu to upload multiple related XSD files.

    -

    Note: Please upload a valid XSD structure. BEXIS2 does not check this kind of validation.

    -

     

    -

    Select XSD File 

    -

     

    - -

    Read Source

    -

    Please specify a name (i.e. display name) for the new metadata structure. You may also enter a root node if only a part of the XSD is to be used (optional).

    -

    Read XSD File

    To find the root node open the XSD Schema file and have a look on the element tags. In the example of ABCD it looks like this.

    -

    img27

    If no root node is selected then the wizard will automatically select the first element which is a complex type. But it is also possible to define the element "DataSet" as root node and the metadata structure starts from this element. The Name of a metadata structure must be unique and the root node must exist.

    -

     

    - -

    Set Parameters

    -

    For the system to handle a dataset at least the title and a description is needed. In this step these two elements, which are typically available in all metadata structures, should be identified and made explicit to the system.

    -

    Set XSD Parameters 

    -

     

    - -

    Summary

    -

     

    -

    The Summary page is an overview about the created metadata structure.

    -

    Summary

    -

     

    -

     

    -

     

    - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml deleted file mode 100644 index 13c4c2180..000000000 --- a/Console/BExIS.Web.Shell/Areas/DCM/BExIS.Modules.Dcm.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - - This wizard will assist you in creating a new dataset. Please select a data structure and a metadata structure below. - Or select a dataset as template to use the metadata structure and the metadata from the selected dataset. - - - - - - -

    This guide will walk you through the basics of data collection including how to upload data and how to import a metadata structure.

    -     - -     - - - - This wizard will assist you in adding a new metadata structure (i.e. schema) to the system. A metadata structure must be defined in XSD schema files. - Since XSD files can be defined in various ways this wizard is build on a few assumptions (e.g. with dependencies). Please consult the Help for more details. - - - - - - - Each user has a personal folder on the server where files are stored temporary. This wizard will assist you in pushing your files to server. You can also see the uploaded files, delete each file, or use these files later, when you want to upload data to a dataset. - - - - - - - This wizard will assist you in uploading data files to the system and adding them to a dataset. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj index d6f4d92c6..38802468d 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/BExIS.Modules.Ddm.UI.csproj @@ -150,7 +150,6 @@ - @@ -215,7 +214,6 @@ - @@ -230,7 +228,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs deleted file mode 100644 index 567eb65eb..000000000 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,20 +0,0 @@ -using BExIS.Utils.Config; -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Ddm.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /ddm/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("DDM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml index c6b830ad5..c92ff3826 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI/Ddm.Manifest.xml @@ -32,11 +32,6 @@ controller="dashboard" action="index" extends="./menubarRoot" /> - - - -

    img1 

    - - - -

     

    - -

    3.1. Mapping Overview

    -Mapping tool is accessible through the Manage Metadata Structure by clicking on the arrow buttons. Mapping could be defined to or from the system. -

    The page of Metadata Structure Mapping is divided into 3 sections. The source is displayed on the left and the target on the right side. All created mappings are displayed in the middle.

    -

    img1 

    -

     

    -

    - Source and target in the left and right side includes two parts: Simple and Complex blocks. First name, last name or full name of a person are examples of Simple elements. A Complex element could be a person. - Search box is provided for each side (source or target) seperatly. -

    - -

    Mappings are connections between the source and the target. There are different connection possibilities between the simple attributes. Generally only the connection between two simple attributes is considered.

    -

    With the aid of a transformation rule, it is possible to cover a wide range of different cases. A transformation rule consists of a RegEx and a mask. With an example you can check the values and the expected result.

    - - -

    3.2 Mapping Examples

    -

    Following is some examples of one to one, one to many and many to one mapping.

    - -Example: One to One -

    This example creates a connection between two titles. All words are separated by a RegEx and then arranged differently via the mask.

    -

    img1 

    -EXAMPLE: One to Many -

    This example creates a connection between a name in one side and the FirstName and the LastName in other side. In the transformation rule, the first and last names are separated from one another by a RegEx and then positioned in the mask via the variable.

    -

    img1 

    -EXAMPLE: Many to One -

    This example creates a connection between the FirstName and LastName by a name. Here is no RegEx needed but the mask ordered from both variables.

    -

    img1

    - -

    3.3. Create a mapping

    -
      -
    1. Choose a simple or complex element from the source.
      2. -
    2. Add Element to the middle section by clicking the orange arrow next to the element.
      3. -
    3. Choose a simple or complex element from the target.
      4. -
    4. Create the mapping by clicking on the create button
      5. -
    5. All available simple elements are listed in the mapping container for this mapping. Draw a line by clicking on one simple element from the source side and drag it to a simple element on the target side.
      6. -
    6. If needed, add RegEx and mask to the transformation rule.
      7. -
    7. Press on the save button after entering values in the blocks.
      8. -
    - -

    3.4. Key overview

    -

    key_overview

    - -

    4. Publishing a Dataset Version

    -

    Prepare the data is from now available for two brokers and a three data repositories.

    -
      -
    • - Brokers: -
        -
      • GFBIO
        • -
      • Pensoft
        • -
      -
      • -
    • - Data Repositories: -
        -
      • GFBIO Collections
        • -
      • Pangaea
        • -
      • Pensoft
        • -
      -
      • -
    - -

    - There is limitation to publish a dataset version:
    - First of all preparing dataset versions is only possible if the metadata is valid.
    - Second is related to the Pensoft. All data prepared for Pensoft must be generated with the GBIF metadata structure. -

    - -

    4.1. Publish

    -

    Publish a dataset is attainable through the Publish tab on the dataset view.

    -

    All available data center are listed in a dropdown. After selcting a data center, system tries to convert the data and the metadata as defined in the submissionConfig.xml. If something fails a warning message will displayed.

    -

     

    -

    There are two types of fails:

    -
      -
    1. The system is not able to convert the data.
      2. -
    2. Metadata is not valid. In this case you can continue the procedure but the metadata.xml is not valid against the exported xsd schema.
      3. -
    -

    img3 

    -

     

    -

    4.2. GFBIO

    -

    Via the GFBIO portal you can start a submission and publish your dataset. Depending on the subject of the data set, a suitable Data Repository is defined. There are different main Types:

    -
      -
    • Pangaea
      • -
    • Collections
      • -
    • ENA
      • -
    -

    Each data repository has different data requirements. BEXIS2 offers an export for Pangea and Collections.

    - - -

    The data for the collections is stored in a zip file includes

    -
      -
    1. Schema - XSD Schema for the metadata
      2. -
    2. Data.*** - Primary Data
      3. -
    3. Data structure - Structure of the primary data
      4. -
    4. Manifest File - General informations about the Dataset
      5. -
    5. Metadata - Metadata informations about the dataset
      6. -
    -

    For the Pangea, the metadata and primary data are stored in a text file.

    - - - -

     

    -

     

    - - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml deleted file mode 100644 index 59329e0e0..000000000 --- a/Console/BExIS.Web.Shell/Areas/DIM/BExIS.Modules.Dim.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - On this page you are able to export metadata to a standard compliant XML file, i.e. ABCD or EML.
    -
      -
    • Please select a metadata structure first (tab)
      • -
    • Select one or more datasets to export
      • -
    • Click the export button to create XML files
      • -
    -     - -     - - - - This guide will walk you through the basics of using data dissemination. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte index fc30602f1..131b62453 100644 --- a/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte +++ b/Console/BExIS.Web.Shell/Areas/PUM/BExIS.Modules.Pum.UI.Svelte/src/routes/importjson/+page.svelte @@ -302,6 +302,11 @@ // apply custom rules from transformations.ts const transformedData = applyTransformations(data); + // remove tags in descr + if (transformedData.abstract) { + transformedData.abstract = stripJatsTags(transformedData.abstract); + } + // Filter data based on mapping.json validatedData.data = filterData(transformedData, mapping); @@ -418,6 +423,15 @@ } + function stripJatsTags(value: string): string { + if (!value) return value; + return value + .replace(/]*>/gi, "") + .replace(/<\/jats:p>/gi, "") + .trim(); + } + + /* ============================================================ FILTER DATA ACCORDING TO MAPPING.JSON diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj index 6a9d59fbc..fe2604465 100644 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/BExIS.Modules.Rpm.UI.csproj @@ -123,7 +123,6 @@ - diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs deleted file mode 100644 index 2cc6de42f..000000000 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,17 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Rpm.UI.Controllers -{ - public class HelpController : Controller - { - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("RPM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml index 89055e887..76008d0c3 100644 --- a/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/RPM/BExIS.Modules.Rpm.UI/Rpm.Manifest.xml @@ -11,11 +11,6 @@ - - - @@ -204,11 +203,9 @@ - - diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs deleted file mode 100644 index bbaf22efb..000000000 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Controllers/HelpController.cs +++ /dev/null @@ -1,16 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Sam.UI.Controllers -{ - public class HelpController : Controller - { - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("SAM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml index 3891160b8..fb30f940d 100644 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Sam.Manifest.xml @@ -59,10 +59,6 @@ controller="Files" action="FileList" argument="Files list" extends="./settingsRoot" />--> - -
    -

    Administration ToC

    -
    -

    1. Overview -

    2. Registration -

       2.1. Login -

    3. Users -

       3.1. Create a user -

       3.2. Edit a user -

    4. Groups -

       4.1. Create a group -

       4.2. Edit a group -

    5. Permissions -

       5.1. Feature Permissions -

       5.2. Datasets Permissions -

    6. Manage Datasets -

    7. API Token - -} - - - -

    1. Overview

    - -

    - By default, only a few components of BEXIS2 are accessible for anonymous users. Any further access to the application is available for authorized users, only. Therefore, Administration module provides probably of user registration that could control by administrators. After a successful registration, user is able to logon to BEXIS2 using its account credentials for authentication.
    - Features. The set of features is fixed and corresponds to the different hierarchical items of the menu bar.
    - Permissions. Within the system, it is possible to add, remove or modify existing permissions on features and datasets. -

    -

     

    -

    2. Registration

    -

    - Registration is accessible through the menu bar. All fields are mandatory and system needs accept of the Terms and Conditions. - To complete successfully the registration process you need to react to a confirmation Email. -

    -

    registration

    -

     

    -

    2.1. Login

    -

    First, press Login button. The system redirects you to the login form and you have to enter your account credentials (username and password). If the login is successful, you will see Dashboard. Otherwise, the system will notify you about the status and reason why the logon was not successful.

    -

    login

    -

     

    -

    3. Users

    -

    Caution! This part of the system is secured. You may not have access to it.

    -

    BEXIS2 provides different features for managing users. These are typically available to system administrators only. Each of them is described in more detail in one of the following subsections.

    -

    users

    -

    3.1. Create a user

    -

    In addition to the self-registration procedure, user accounts may also be created by an administrator. This feature is available from Setup > Manage Users. Please press the Create button. A modal window will pop up that contains the user creation form. Similar to the self-registration, the system supports you with validation on all information entered.

    -

    create_user

    -

     

    -

    3.2. Edit a user

    -

    Within BEXIS2 you are able to display and modify user information. For security and usability reasons, the system allows modification only for certain parts of the user information. Please go to Setup > Manage Users and press the Edit button of the respective user. You are now able to alter the user information. Changes are committed to the system when you press the Save button.

    -

    For any given user memberships to certain groups need to be specified via the tab Membership.

    -

    You can change the status easily by (un)select the corresponding checkbox.

    -

    edit_user

    -

     

    -

    4. Groups

    -

    Caution! This part of the system is secured. You may not have access to it.

    -

    BEXIS2 provides different features for the managing groups. They are typically available to system administrators only. Each of them is described in more detail in the following subsections.

    -

    groups 

    -

    4.1. Create a group

    -

    This feature is available from Setup > Manage Groups. Please press the Create button. A modal window will pop up that contains the group creation form. The system supports you with validation on all information entered.

    -

    create_group 

    -

     

    -

    4.2. Edit a group

    -

    Within BEXIS2 you are able to display and modify group information. Please go to Setup > Manage Groups and press the Edit button of the respective group. You are now able to alter the group information. Changes are committed to the system once you pressed the Save button.

    -

    For any given user memberships to certain group need to be specified via the tab Membership.

    -

    You can change the status easily by (un)select the corresponding checkbox.

    -

    edit_group 

    -

     

    -

    5. Permissions

    -

    Caution! This part of the system is secured. You may not have access to it.

    -

    Permission is a rule that contains certain security regulations. In general, it is possible to set a rule on both, users and groups.

    -

    The security system of BEXIS2 distinguishes between two types of permissions. On the one hand, there are feature permissions, which allow or prohibit the access to well-defined and delimited areas of the application. This type of permissions is working on functional objects (e.g. actions that should be performed) - so called Features. On the other hand, data permissions provide the ability to protect real data (e.g. datasets, research plans and so on).

    -

     

    -

    5.1. Feature Permissions

    -

    To be able to modify features, Please go to Setup > Manage Feature Permissions. This will bring up a page with a tree on the left side.

    -

    Selecting a checkbox in the navigation tree (e.g. Search) will make that feature accessible without authentication (public access). Please use with care!

    -

    By clicking a feature name (a node in the tree), the system will show a table on the right side (see below). This table contains all subjects (users and groups) and their feature permission status. You may grant or deny permissions for individual users or groups using the radio buttons. If a permission is not explicitly set (i.e None) permissions are inherited from up level features. Inherited permissions are shown in the first column as effective permissions.

    -

    features 

    -

     

    -

    5.2. Entity Permissions

    -

    The security system of BEXIS2 is working on both, functional (features) and non-functional (entities) items. Please go to Setup > Manage Entity Permissions if you like to manage access to entities (datasets).

    -

    By selecting a dataset (i.e. a row in the table), the system will show a second table underneath the first one, which contains all subjects (users and groups) and their different data permission statuses regarding the selected dataset. On this page, you are also able to alter the different kinds of data permissions for a selected dataset.

    -

    Selecting the checkbox in the first column (i.e. IsPublic) will allow public access to that dataset without any authentication.

    -

     

    -

    datasets 

    -

     

    -

    In general, the system works on six different data permission types:

    -
  • Read: allow/deny read & download access to primary data
    • -
  • Update: allow/deny manipulation (upload and update) of primary data
    • -
  • Delete: allow/deny deletion of the whole dataset
    • -
  • Grant: allow/deny to give permission to other users or groups
    • -

     

    -

    6. Manage Datasets

    -

    Via menu in Setup > Manage Datasets you are able to see a list of Datasets.

    -

    In this list you can see the status of each dataset and some useful actions for the maintenance of a dataset.

    -

    maintenance 

    -

    There are two ways to delete a dataset:

    -

    Delete: this function tags a dataset to exclude it from nearly all features of the system (e.g. search). But the dataset itself will stay inside the database. So later on you are able to recover the dataset - if needed.

    -

    Purge: the dataset will be removed from the system at all (incl. removal of data permissions, metadata and primary data). There is no way to rollback that action.

    -

    Note that if you purge a dataset, you cannot recover it at all.

    -

     

    -

    7. API Token

    -

    - In general, the APIs of BEXIS2 are protected by both mechanisms, authentication and authorization. In contrast to the login where usual credential are used, the APIs are using a personalized token for authentication. Within the user menu, each user has the possibility to show her/his own token. Afterwards, that token can be used for the APIs. -

    -

    token 

    - -

     

    -

     

    - - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml deleted file mode 100644 index 381b48741..000000000 --- a/Console/BExIS.Web.Shell/Areas/SAM/BExIS.Modules.Sam.UI/Views/Help/Informations.xml +++ /dev/null @@ -1,108 +0,0 @@ - - - - -

    In the case of any problems with authorization, please contact with your administrator.

    -     - -     - - -

    Through this interface you can login into the system.

    -

    If you have not a username, you need to register into the system first.

    -     - -     - - -

    This page summarizes your personal account information. Furthermore, you are able to edit that data, but there are two important facts you should be aware of:

    -
      -
    1. - Password Change - You need to enter both, Password and Confirm Password. -
      2. -
    2. - Security Question/Answer - You need to enter both, Security Question and Security Answer. -
      3. -
    -

    Otherwise, the abovementioned properties aren't changed.

    -     - -     - - - - Here you are able to manage how users (or groups) have access to individual datasets. - Please select a dataset in the table below and specify who should have permissions to Information, update, delete, download data, or who is able to grant access to other users (Note: metadata is always free). - Ticking the checkboxes "public access" in the upper table will make a dataset accessible without authentification (public access to primary data). Please use with care! - By default only the creator of a dataset (in the system) has full access, all other permissions are not set, which means access is denied. - Grants for individual users rule out higher level settings for groups. - Please note that any change will take effect immediately without further confirmation or save/submit action. - - - - - - - With this interface you are able to see a list of Datasets. In this list you can see the status of each dataset and some useful actions for the maintenance of a dataset. - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - This maintenance tool is meant for administrators only. All datasets are listed with their internal ID, status, and the option to remove them from the system. Use with care! - - - - - - - Here you are able to manage how users (or groups) have access to individual system features or entire modules. - Please click on the name in the tree structure on left to Information individual permissions. - Ticking the checkboxes in the navigation tree will make a feature accessible without authentification (public access). - Please use with care! - By default feature permissions are not set, which means access is denied unless access permissions are explicitly granted or inherited from an upper level feature (e.g. module). - Individual grants on features rule out higher level settings. Effective permissions are shown in the first column of the table. - Please note that any change will take effect immediately without further confirmation or save/submit action. - - - - - - - With this interface you are able to manage groups. New groups can be added with the "Create" button. Existing groups can be edited (properties, members, delete) using the "Edit" button. - - - - - - - This guide will walk you through the basics of using administration parts including how to registrate or log on, how to manage users or groups and how to manage permissions. - - - - - - - With this interface you are able to manage users. New users can be added with the "Create" button. Existing users can be edited (properties, memberships, delete) through the "Edit" button. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj b/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj index 9c716d380..9bc62da87 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj +++ b/Console/BExIS.Web.Shell/Areas/VIM/BExIS.Modules.Vim.UI.csproj @@ -44,7 +44,6 @@ 4 - @@ -298,12 +297,10 @@ - Designer - Designer diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs b/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs deleted file mode 100644 index 54075edbb..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Controllers/HelpController.cs +++ /dev/null @@ -1,19 +0,0 @@ -using BExIS.Utils.Helpers; -using System; -using System.Web.Mvc; -using Vaiona.Web.Mvc.Modularity; - -namespace BExIS.Modules.Vim.UI.Controllers -{ - public class HelpController : Controller - { - // - // GET: /VIM/Help/ - - public ActionResult Index() - { - string helpurl = ModuleManager.GetModuleSettings("VIM").GetValueByKey("help").ToString(); - return Redirect(ManualHelper.GetUrl(helpurl)); - } - } -} \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml b/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml deleted file mode 100644 index 6eb9d333e..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Index.cshtml +++ /dev/null @@ -1,72 +0,0 @@ -@section Information -{ - This guide will walk you through the basics of visualization. -} -@section leftPane{ -
    -

    Visualization ToC

    -
    -

    1. Overview -

    2. Select Ranges -

       2.1. Select category -

       2.2. Select Time -

       2.2. Time Slider -
    -} - - -

     

    -

     

    - -

    1. Overview

    -

    - Visualization or in other words the visual representation of data in an easily comprehensible form is the feature of the visualization module for BEXIS2. User of BEXIS2 is able to get a quick overview of the system behaviour with looking at diagrams. - Visualization is accessible through setup in the main menu.
    -

    -

     

    -

    all

    -

     

    -

    2. Select Ranges

    -

    - Visualization provides diagrams depend on the selected ranges in different dropdown lists. There is two different lists to control the diagram. - One is to select the kind of data and one is to select the time range.
    -

    -

    2.1. Select Category

    -

    - On the first view, when the selector shows "Select a category", you can see a histogram with data of created and deleted datasets. - The current version of the BEXIS2 makes you able to see the statistic of system activities, created datasets and deleted datasets over time.
    -

    -

    all

    - -

    2.2. Select Time

    -

    - In the drop-down list "Select time, you can find the past years. By default, the chart displays the data distribution over the entire time from the first activities.
    - Select a specific year and see the statistic for only that year, separated in twelve months.
    -

    -

    all

    - -

    2.3. Time Slider

    -

    - If you do not like to see all data behaviour from the first activity to the end, you can select a period by the help of the time slider..
    -

    -

    all

    - -

     

    -

     

    - Go to top \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml b/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml deleted file mode 100644 index 59329e0e0..000000000 --- a/Console/BExIS.Web.Shell/Areas/VIM/Views/Help/Informations.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - On this page you are able to export metadata to a standard compliant XML file, i.e. ABCD or EML.
    -
      -
    • Please select a metadata structure first (tab)
      • -
    • Select one or more datasets to export
      • -
    • Click the export button to create XML files
      • -
    -     - -     - - - - This guide will walk you through the basics of using data dissemination. - - - -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml index 978589de3..f4d877727 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml +++ b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Manifest.xml @@ -16,9 +16,5 @@ controller="visualization" action="index" extends="./settingsRoot" /> -     \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json index 6db207bee..8a33564f9 100644 --- a/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json +++ b/Console/BExIS.Web.Shell/Areas/VIM/Vim.Settings.json @@ -3,12 +3,6 @@ "name": "Visualization", "description": "stats about datasets", "entries": [ - { - "key": "help", - "title": "Help URL", - "value": "", - "type": "String", - "description": "URL to the manual. If empty, it links to the latest manual from BEXIS2" - } + ] } \ No newline at end of file diff --git a/Console/BExIS.Web.Shell/Controllers/MenuController.cs b/Console/BExIS.Web.Shell/Controllers/MenuController.cs index 7f85a43b2..c4b1620d0 100644 --- a/Console/BExIS.Web.Shell/Controllers/MenuController.cs +++ b/Console/BExIS.Web.Shell/Controllers/MenuController.cs @@ -3,6 +3,7 @@ using BExIS.UI.Models; using BExIS.Web.Shell.Helpers; using System; +using System.Linq; using System.Web; using System.Web.Mvc; using Vaiona.Web.Extensions; @@ -56,6 +57,8 @@ public JsonResult Index() menu.LaunchBar = MenuHelper.MenuBar("lunchbarRoot"); menu.MenuBar = MenuHelper.MenuBarSecured("menubarRoot", userName); menu.Settings = MenuHelper.MenuBarSecured("settingsRoot", userName, true); + MenuHelper.AdditionalHelpBar(menu.LaunchBar.FirstOrDefault(i =>i.Title.Equals("Help"))); + menu.AccountBar = MenuHelper.AccountBar(isAuthenticated, userName); diff --git a/Console/BExIS.Web.Shell/General.Settings.json b/Console/BExIS.Web.Shell/General.Settings.json index fe81621b6..f20526dc6 100644 --- a/Console/BExIS.Web.Shell/General.Settings.json +++ b/Console/BExIS.Web.Shell/General.Settings.json @@ -103,82 +103,97 @@ "description": "send or excluded exception sending via email." }, { - "key": "landingPage", - "title": "Landing Page (without login)", - "value": "ddm, publicsearch, index", - "type": "String", - "description": "User is not logging in -> app goes to e.g. (ddm, publicsearch, index). If no destination is entered, the landingpage.htm is loaded from the tenant/content/landingpage.htm" - }, - { - "key": "showMenuOnLandingPage", - "title": "Show menu on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide menu on your own created landing page" - }, - { - "key": "showHeaderOnLandingPage", - "title": "Show header on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide header on your own created landing page" - }, - { - "key": "showFooterOnLandingPage", - "title": "Show footer on landing page", - "value": "true", - "type": "Boolean", - "description": "Show or hide footer on your own created landing page" - }, - { - "key": "landingPageForUsers", - "title": "Landing Page after login for users with permission", - "value": "ddm, search, index", - "type": "String", - "description": "User logged in, but does not have permission to view the page; shell, home, nopermission is by default; Alternatives must be in a module NOT shell" - }, - { - "key": "landingPageForUsersNoPermission", - "title": "Landing Page after login for users with no permission", - "value": "shell, home, nopermission", - "type": "String", - "description": "Landing page for users, after logging in successfully without permission." - }, - { - "key": "systemEmail", - "title": "System E-Mail Address", - "value": "david.schoene@uni-jena.de", - "type": "String", - "description": "All administrative information will be sent to this email." - }, - { - "key": "usePersonEmailAttributeName", - "title": "Use Person E-Mail Attribute Name", - "value": false, - "type": "Boolean", - "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." - }, - { - "key": "personEmailAttributeName", - "title": "Person E-Mail Attribute Name", - "value": "Email", - "type": "String", - "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." - }, - { - "key": "useMultimediaModule", - "title": "Use Multimedia Module?", - "value": true, - "type": "Boolean", - "description": "This flag turns on/off the Multimedia Module." - }, - { - "key": "faq", - "title": "FAQ", - "value": "https://github.com/BEXIS2/Core/wiki/FAQ", - "type": "String", - "description": "FAQ URL. Can link to an external page." - } + "description": "...", + "key": "help", + "title": "Addition Help Links", + "type": "EntryList", + "value": [ + { + "description": "FAQ", + "key": "helpLink", + "title": "Url", + "type": "String", + "value": "https://github.com/BEXIS2/Core/wiki/FAQ" + } + ] + }, + { + "key": "landingPage", + "title": "Landing Page (without login)", + "value": "ddm, publicsearch, index", + "type": "String", + "description": "User is not logging in -> app goes to e.g. (ddm, publicsearch, index). If no destination is entered, the landingpage.htm is loaded from the tenant/content/landingpage.htm" + }, + { + "key": "showMenuOnLandingPage", + "title": "Show menu on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide menu on your own created landing page" + }, + { + "key": "showHeaderOnLandingPage", + "title": "Show header on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide header on your own created landing page" + }, + { + "key": "showFooterOnLandingPage", + "title": "Show footer on landing page", + "value": "true", + "type": "Boolean", + "description": "Show or hide footer on your own created landing page" + }, + { + "key": "landingPageForUsers", + "title": "Landing Page after login for users with permission", + "value": "ddm, search, index", + "type": "String", + "description": "User logged in, but does not have permission to view the page; shell, home, nopermission is by default; Alternatives must be in a module NOT shell" + }, + { + "key": "landingPageForUsersNoPermission", + "title": "Landing Page after login for users with no permission", + "value": "shell, home, nopermission", + "type": "String", + "description": "Landing page for users, after logging in successfully without permission." + }, + { + "key": "systemEmail", + "title": "System E-Mail Address", + "value": "david.schoene@uni-jena.de", + "type": "String", + "description": "All administrative information will be sent to this email." + }, + { + "key": "usePersonEmailAttributeName", + "title": "Use Person E-Mail Attribute Name", + "value": false, + "type": "Boolean", + "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." + }, + { + "key": "personEmailAttributeName", + "title": "Person E-Mail Attribute Name", + "value": "Email", + "type": "String", + "description": "To activate the linkage between between user email and a party email set Use Person E-Mail Attribute Name to true and define the party party attribute. If one of the email addresses is changed the other is changed as well." + }, + { + "key": "useMultimediaModule", + "title": "Use Multimedia Module?", + "value": true, + "type": "Boolean", + "description": "This flag turns on/off the Multimedia Module." + }, + { + "key": "faq", + "title": "FAQ", + "value": "https://github.com/BEXIS2/Core/wiki/FAQ", + "type": "String", + "description": "FAQ URL. Can link to an external page." + } ] } diff --git a/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs b/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs index cc05617c4..0baac5ec1 100644 --- a/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs +++ b/Console/BExIS.Web.Shell/Helpers/MenuHelper.cs @@ -2,6 +2,7 @@ using BExIS.Security.Services.Authorization; using BExIS.Security.Services.Objects; using BExIS.UI.Models; +using BExIS.Utils.Config; using System; using System.Collections.Generic; using System.Linq; @@ -215,6 +216,36 @@ public static List ExtendedMenu(XElement list) return menuItems; } + /// + /// defaul menubar load with bar name like + /// menubarRoot + /// Accountbar + /// + /// + /// + public static List AdditionalHelpBar(MenuItem help) + { + List menuItems = help.Items; + + var help_list = GeneralSettings.GetValueByKey("help") as List; + + // go throw each item + foreach (var link in help_list) + { + if (link != null) + { + MenuItem menuItem = new MenuItem(); + //get title of the item + menuItem.Title = link.Description; + menuItem.Url = link.Value; + + menuItems.Add(menuItem); + } + } + + return menuItems; + } + private static string getUrl(XElement element) { StringBuilder sb = new StringBuilder(); diff --git a/Console/BExIS.Web.Shell/Shell.Manifest.xml b/Console/BExIS.Web.Shell/Shell.Manifest.xml index eb531a1a3..a2c9510bd 100644 --- a/Console/BExIS.Web.Shell/Shell.Manifest.xml +++ b/Console/BExIS.Web.Shell/Shell.Manifest.xml @@ -36,11 +36,7 @@ extends="." /> - - + Date: Fri, 30 Jan 2026 17:24:52 +0100 Subject: [PATCH 12/29] update workspace link #2299 --- Console/Workspace | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Console/Workspace b/Console/Workspace index 055d38af6..c127f4bdf 160000 --- a/Console/Workspace +++ b/Console/Workspace @@ -1 +1 @@ -Subproject commit 055d38af6c152f56236f0411621e18f4c5e4c680 +Subproject commit c127f4bdf482e2e5253fa38ce3aa686da5823188 From 3d9bcf30220b68378b5a13be31b0892435e757fb Mon Sep 17 00:00:00 2001 From: geofranzi Date: Fri, 30 Jan 2026 17:57:25 +0100 Subject: [PATCH 13/29] Add minimal tag request workflow #1735 --- .../src/routes/taginfo/TagInfoEdit.svelte | 85 ++++++++++++++- .../src/routes/taginfo/services.ts | 34 ++++++ .../routes/taginfo/table/tableOptions.svelte | 57 ++++++---- .../Controllers/TagInfoController.cs | 102 +++++++++++++++++- Console/Workspace | 2 +- 5 files changed, 257 insertions(+), 23 deletions(-) diff --git a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/src/routes/taginfo/TagInfoEdit.svelte b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/src/routes/taginfo/TagInfoEdit.svelte index 553648627..03f135846 100644 --- a/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/src/routes/taginfo/TagInfoEdit.svelte +++ b/Console/BExIS.Web.Shell/Areas/DDM/BExIS.Modules.Ddm.UI.Svelte/src/routes/taginfo/TagInfoEdit.svelte @@ -4,9 +4,18 @@ Table, notificationStore, notificationType, - ErrorMessage + ErrorMessage, + TextArea } from '@bexis2/bexis2-core-ui'; - import { add, get, save, updateSearch } from './services'; + import { + add, + get, + save, + updateSearch, + sendRequestForTagApproval, + isCurator, + isCuratorRequired + } from './services'; import { tagInfoModelStore, withMinorStore, originalTagInfoModelStore } from './stores.js'; import TablePublish from './table/tablePublish.svelte'; @@ -50,8 +59,18 @@ console.log('🚀 ~ reload ~ tagInfoModelStore:', $tagInfoModelStore); } + let isCuratorUser: boolean = false; + let isCuratorRequiredForTags: boolean = true; onMount(() => { + isCurator().then((res) => { + isCuratorUser = res; + console.log('🚀 ~ onMount ~ isCuratorUser:', isCuratorUser); + }); + isCuratorRequired().then((res) => { + isCuratorRequiredForTags = res; + console.log('🚀 ~ onMount ~ isCuratorRequired:', isCuratorRequiredForTags); + }); reload(); }); @@ -117,6 +136,25 @@ }); } } + + function sendRequestForTagApprovalFn(value: string) { + const data = { message: value, id: id }; + sendRequestForTagApproval(data).then((response) => { + if (response.status === 200) { + notificationStore.showNotification({ + notificationType: notificationType.success, + message: 'Request for tag approval sent.' + }); + } else { + notificationStore.showNotification({ + notificationType: notificationType.error, + message: 'Request for tag approval not sent.' + }); + } + }); + } + + let requestTagApprovalMessage: string = ''; {#await promise} @@ -125,6 +163,49 @@ {:then model}

    Release Tag Management - Dataset ID {id}

    + +
    +

    + To make your dataset visible in the search, at least one released dataset version is required. {#if !isCuratorUser && isCuratorRequiredForTags}Only + curators can create releases.{/if} +

    +

    + Once released, the specific dataset version will be visible to users. As long as you only make + changes to the metadata, the latest version is shown automatically. If changes are made to the + data itself, a new release request is required so that these updates become visible to all + users. +

    + {#if !isCuratorUser && isCuratorRequiredForTags} +

    + Use the form below to request a new release from a curator. Please provide a short release + message and specify the version you refer to (if not specified the latest version will be + used). +

    +

    + The curator will review your request, create the release accordingly, and may contact you if + needed. +

    +
    +
    +