109 results found

1. Ability to integrate our Ingest tool with Rosetta

   We are looking at supporting the ability to add a new format to our Ingest tool, in conjunction with this we would like that to trigger some type of API call to Rosetta and add the file format as an allowed format as well.

   In Rosetta you can add a new file extension in the Submission Format area of the UI. We have provided the option to add a new format in our Ingest tool, So once they do this, we would like this to trigger an some type of API call to Rosetta and add the new file extension as an allowed file extension without having to go into the UI and add the file extension manually in the Submission Format location.

   We are looking at supporting the ability to add a new format to our Ingest tool, in conjunction with this we would like that to trigger some type of API call to Rosetta and add the file format as an allowed format as well.

   In Rosetta you can add a new file extension in the Submission Format area of the UI. We have provided the option to add a new format in our Ingest tool, So once they do this, we would like this to trigger an some type of API call to Rosetta and add the new file extension… more

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Environment & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Allow institutional parameters for (custom) plugins

   In a consortial landscape a plugin may be used by several institutions. However, each institution may need to use different parameters for a shared plugin.

   To give examples, consider these two business cases:
   (1) A plugin utililzes proprietary 3rd party software that is licenced per institution. In such case we must ensure that only the institutions that actually pay the licence fee have access to the functionality. The license key would have to be configured per institution.
   (2) A PDF migration plugin can take different input parameters which determine the output format to be created (e.g. to PDF/A-1b vs. PDF/A-2b). An institution will want to use these input criteria when defining the mirgration process as part of preservation action from within the institution itself.

   While in the case of processes parameters can currently be defined within an institution when scheduling the process (e.g., for fixity task which checksum algorithm should be used), parameters of plugins can currently not be passed to the institutional level. We would like to see this change in order to use plugins in a more flexible and institutional-friendly way. Currently there is no information available if and how this can be achieved for custom plugins. It might also make sense in the case of some bundled plugins, e.g., if an institution would like to use a different DROID max byte scan config than another one.

   In a consortial landscape a plugin may be used by several institutions. However, each institution may need to use different parameters for a shared plugin.

   To give examples, consider these two business cases:
   (1) A plugin utililzes proprietary 3rd party software that is licenced per institution. In such case we must ensure that only the institutions that actually pay the licence fee have access to the functionality. The license key would have to be configured per institution.
   (2) A PDF migration plugin can take different input parameters which determine the output format to be created (e.g. to PDF/A-1b vs. PDF/A-2b).… more

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs & Plug-ins  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Take account of the METS mimetype attribute during file ingest

   The METS standard has a mimetype attribute on files "<file MIMETYPE="application/pdf" ... /> but this information is currently ignored by Rosetta during the file-type identification process on ingest.

   Mimetye should be at least as reliable as file extensions (because mimetype is a standard, is actively maintained and widely use by a good portion of software for identifying file types).

   In particular, recognising mimetypes is likely to greatly increase the ease of ingest of content from internet-facing content management systems where it is very widely used

   See also https://tools.ietf.org/html/rfc6838

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Ingest  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. encrypt all update channels

   After experiencing some problems with Rosetta's Format Library update mechanism (see SC 00423700 "error while updating Format Library [Rosetta 5.1.0.2]", handled by Paul), we got thinking about Rosetta updates in general. Currently, all updates are downloaded through an unencrypted connection. This includes:
   - Rosetta updates (major, minor, service packs, hotfixes) and their checksum files (!)
   - Oracle updates and their checksum files
   - PDS updates (presumably)
   - Format Library updates
   Due to this, there's no way to verify authenticity of ExLibris' servers and the integrity of the update packages/the checksums. All information that are downloaded from ExLibris' servers must be seen as tainted and cannot be trusted, because the transmission is unguarded. Even though ExLibris provides checksums for some (all?) of the updates provided, verifying that information against the calculated fixity from the update packages will not provide any additional security, as both the patches and the checksums could be tampered with in a man-in-the-middle attack. This contradicts current best practices in IT security and is considered a risk for the integrity of the repository software and data. Also, if I understand the comment from SC 00423700 correctly, the current FTP password for Format Library updates is hardcoded into Rosetta when it really shouldn't be.

   A possible update scenario for major/minor/servicepack updates could look as follows: on Rosetta installation, customers provide ExLibris with a PublicKey specific to that Rosetta installation. To reduce administrative overhead, several/all servers of the same multi server environment could share the same key. That key is added to the ExLibris update servers' list of authorized keys, thus allowing the customers' servers to connect. During the update, the "util sp" command queries the user for the key passphrase and connects to ExLibris' update servers via SFTP to download the patch packets and fixity information. The fixity information is then compared against the calculated fixity of the patches downloaded previously.

   A possible update scenario for hotfixes could look as follows: users manually connect to the update server from the Rosetta server CLI using the SSH key. The user then downloads and validates the patch packets and fixity information. Alternatively, the update procedure is unified with the process used for all other updates (btw, is there any technical requirements this hasn't already happened?) and the procedure described above is used.

   Updates for PDS and Oracle could be distributed in a way similar to the one described in the hotfixes paragraph.

   We've noticed that the first step on improving update security is already done by providing Format Library updates via SFTP (set General Parameter "usesftp" to "true"). However, this is foiled by Rosetta checking for FL updates via plain unencrypted FTP on every reload of the "Home => Preservation => Manage Format Library Version" page. Apparently, that step fails if "usesftp" is set to "true" in Rosetta 5.1.x.

   Please keep in mind that publishing and enforcing (!) a policy against short keylengths/weak crypto algorithms/weak kex algorithms is highly recommended when using SFTP/SCP.

   After experiencing some problems with Rosetta's Format Library update mechanism (see SC 00423700 "error while updating Format Library [Rosetta 5.1.0.2]", handled by Paul), we got thinking about Rosetta updates in general. Currently, all updates are downloaded through an unencrypted connection. This includes:
   - Rosetta updates (major, minor, service packs, hotfixes) and their checksum files (!)
   - Oracle updates and their checksum files
   - PDS updates (presumably)
   - Format Library updates
   Due to this, there's no way to verify authenticity of ExLibris' servers and the integrity of the update packages/the checksums. All information that are downloaded from ExLibris' servers must be… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Make Standard Upload procedure for 3A configurable (Applet vs. manual upload)

   When adding representations via the 3A workbench, the default procedure is the applet upload. Due to security settings, the applet may not be available in some environments. In this case, the user has to click the "Load the files manually" link located on the left to then switch to the manual upload procedure, which works fine.
   To avoid these extra steps it would be nice to set the default upload procedure (applet or manual) for 3A workflows via a general parameter.

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Ingest  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Bulk delete of Processes

   We can have 100s of processes located under the Data Management tab and we would like the ability to mark some or all of the processes and then delete them in bulk

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Data Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Planned  ·  AdminDaniel Greenberg (Product Manager, Ex Libris) responded

   Included in 6.0

7. make

   As the set of supported operating systems is known and limited, it would be great to have a Rosetta installation path that uses the distributions' packet manager (e. g. yum) for the initial installation and all upgrade processes. This could facilitate disaster recovery, improve availability and reduce the time needed for upgrades (you could just run "yum upgrade"). DB connectivity etc. could be checked during the package installation.

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Support Indexing of Date Range

   Enable indexing of a range between start and end values.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Data Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Adi Alter responded

   Submitted by Ex Libris PM on behalf of our customers

9. Deactivate Institution

   Enable deleting an institution that had content already deposited into it. This should be enabled only if all the IEs were already deleted.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Administration  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Adi Alter responded

   Submitted by Ex Libris PM on behalf of our customers