Rosetta

Your feedback matters to us. Help us improve Rosetta by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Publishing Sync Job - View Log

    hen running a Publishing Sync Job and looking at the assciated 'View' we get the following information

    Mon Jan 07 09:06:40 AEST 2019 INFO sync all configurations for IE publishing
    Mon Jan 07 09:06:40 AEST 2019 INFO sync the configurationId: 18981614
    Mon Jan 07 09:06:41 AEST 2019 INFO sync the profileId: 18981613
    Mon Jan 07 09:06:41 AEST 2019 INFO Handling new IEs
    Mon Jan 07 09:06:41 AEST 2019 INFO Handling Removed IEs
    Mon Jan 07 09:06:41 AEST 2019 INFO Handling updated IEs
    Mon Jan 07 09:06:41 AEST 2019 INFO Finished sync for the profileId: 18981613
    Mon Jan 07 09:06:41 AEST…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
  2. Rosetta SIP Producer ID

    Carried out a search for SIP ID in the 'Rosetta Management | Submissions:Search for SIPs' -- the results returned provides the 'Producer Id' -- you can grab the ID and use it to find the producer name -- it may be useful to not only include the producer ID but to also include the producer name - this may save that additional step of checking producer ID t get the producer's name

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  3. Rosetta UX - scheduled Jobs management

    I am not sure what the default sort sequence is for the 'Scheduled Jobs Management' but it would be good if the default sort sequence is by 'Name'

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  4. Default IE Export Location

    Would it be possible to change the default export path for DRPS Prod to ...
    /opt/drps/export/dept/CHD/WIP/Exports/[USER]
    instead of ...
    /opt/drps/pipeline/shared/operational_shared/staff_work_area/[USER]/export/ies
    or perhaps just /opt/drps/export/dept/CHD/WIP/Exports if including the [USER] is too much trouble
    It would also be nice if the default path in DCMS Prod could be ...
    /opt/dcms/pipeline/dept/CHD/WIP/Exports

    We are aware of the IE export web service. We want to be able to click on the export IE link in advanced search and have it immediately start exporting to a specific path

    See case: 00474798

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  5. CMS Update

    submitted on behalf of Michele Lindlar

    Sometimes it's neccessary to update our cms metadata. if a librarian changes a record in the external cms-system, we want to update the record in rosetta too, but there's no task that works accordingly. we'd be really happy if there would be a task chain or a process that re-harvest existing cms-records.

    We currently integrate two catalogue systems via SRU in Rosetta: Aleph and Pica. Both systems are integrated uni-directoinal, as in a Rosetta flag is not available in either cataloguing system. As we are integrating the union catalogues which are held by third…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
  6. Enable re-enrichment with CMS records

    Rosetta knows two CMS integration options: unidirectional and bi-directional. The bidirectional integration requires a Rosetta flag to be set in the CMS system. Via the flag, all Rosetta-relevant records from the CMS can be gathered and the metadata pool within Rosetta updated in bulk on a regular basis. However, institutions may be using a CMS for enrichment which belongs to a different / external institution, making the addition of a Rosetta-flag within the CMS system impossible.
    This is where the unidirectional enrichment comes to play. The CMS is queried via SRU integration and records are pulled into Rosetta. The pre-requisite…

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  7. UI interface - Repository | General Settings | Events Configuration

    It wouls be greate if we could sort the display by 'Event Type' as this will allow easier matching to the Rosetta Configuration manul Appendix C whch lists events by ID number

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  8. provide Rosetta developer previews

    ExLibris' current mode of releasing new Rosetta versions is to announce a rough time slot ("April this year") for that new version/minor-release/servicepack/hotfix, release it and deliver a list of changes along with the new release. Up until the actual release, ExLibris will only give a very general roadmap of the planned changes. While this is an easy approach for ExLibris, it's hard for the customers to prepare for the release. Therefore, I propose for ExLibris to provide pre-release versions of Rosetta in order to enable developers to adapt their software (i.e. Submission Applications) to new features, changed API behaviour etc.…

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  9. Profiles for Rosetta-Aleph-Integration

    we are using the Rosetta-Aleph-Integration in both directions:
    1. creating the CMS-record in Rosetta and
    2. setting the Rosetta-flag in Aleph as well as updating the Aleph record with the URN created in Rosetta.
    In the past there was only one target field for the URN and the assignCMS task with updateURNTask worked without problems.

    Due to changes in the cataloging rules - we are using now the international RDA-rules - we have to deal now with different target fields in Aleph for the URN depending on the type of material: e-only e-books, digital reproductions of printed books, online versions…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  10. Counter / SUSHI support in Rosetta

    Increasingly libraries and consortia are using counter / sushi to measure usage of digital and electronic resources across disparate parts of their holdings.

    If holdings being held in Rosetta are to be valued by the broader institutions funding and maintaining those resources, we need to be able to report usage using the counter and sushi protocols (which ExLibris has already demonstrated knowledge of in their support in ALMA and 265 services).

    Key features would be basic counter and sushi reporting; use of IP ranges and user groups already defined in Rosetta for reporting; and grouping or content by already defined…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  11. UI interface - Deposits: Delivery XSL Files | Details xsl viewer

    i have been working in the XSL viewer / editor -- to make it readable i have to copy and paste the information out of the XSL window -- reformat the information to make it readable -- however when I paste the reformatted XSL file into the Rosetta XSL editor the formatting gets lost -- for example <xsl:for-each> all of the information is wrapped back to a single line -- it would be great if the formatting is maintained in the Rosetta XSL editor

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  12. Rosetta UX

    I am currently working in Rosetta 5.4 and there are a couple of UX isues that would make using the prodiuct a lot easier.

    One of these is on the pull down list. It pwiuld be good if the pull-down lists were sorted alphabetically - for example when adding a New Deposit Material flow when I access the 'Select conent structure' the list that is display is in some sort of order but it is definettly not alphabetical

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  13. 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…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base