by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    Bonjour l'équipe,
    nous avons un problème pour accéder à l'interface du prêt (Circulation). Le browser affiche le message "Loading..." et une page blanche. En fait, il n'arrive pas accéder à l'URL ".../patrons/logged_user" (404 - Not found). Vous avez le même comportement sur ils.test.rero.ch
    Avez-vous une idée pour ce problème ?
    (nous utilisons le login "admin" pour le moment)
    Merci,
    Benoit
    Aboubakr Aly Badr
    @BadrAly
    Salut Benoit,
    J’espère que tout va bien.
    Il ne faut pas utiliser le login "admin" pour les fonctionnalités professionnelles (circulation, catalogage, etc.).
    Actuellement, les utilisateurs ayant les rôles “staff" et “cataloguer" peuvent avoir accès à la circulation/catalogage.
    Pour voir la liste des utilisateurs actuellement configurés, voir le menu “Administrer", puis “Utilisateurs"
    Veuillez consulter les fichiers suivants, pour plus d'informations:
    Configurations d’utilisateurs : reroils_data/data/users.json
    Chargements d'utilisateurs : reroils-app/deployment/populate.sh (ligne #45)
    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    Merci Aly.
    sinux334
    @sinux334
    Hello. I just wanted to get some insights in actual rero-ils and wondered that the distributed dockerfile calls for rero-ils-base:latest which isn't available through dockerhub. If I follow install.rst the proposed Dockerfile is calling for rero/rero-ils:dev which isn't available. Am I doing something wrong? regards, simon
    Johnny Mariéthoz
    @jma
    @sinux334 we are refactoring the rero-ils application to be more invenio compliant. We will release it probably in two or three weeks. In the meantime, you can try the current master from github: https://github.com/rero/rero-ils, but the documentation is not uptodate. See the PR: rero/rero-ils#74 for more details.
    sinux334
    @sinux334
    @jma ok, thank you!
    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    Hi guys,
    We have installed the release 0.23 of RERO-ils.
    In the circulation module, when we checkout a book, the system calculates the "due_date" using the params defined in our cipo.
    It's works well for the date but, by default, it takes the time of the transaction.
    Example:
    we define a checkout of 3 days in the CIPO
    We do a checkout this morning at 10:00. The system fixes the due date at today + 3days = 2019-08-03 10:00
    it depends of the institution but we think it's better to let the patron checkin the book before the end of the day no ?
    To fix this on our side, in ext.py, we have used the signal "before_record_update" to change the time of the due_date.
    So now, we do a checkout and the due date is set at now + 3days = 2019-08-03 23:59
    By default, the system could use the closing time defined for the library settings, or a default value (let's say 23h59)
    What do you think ?
    Ben
    Nicolas Prongué
    @pronguen

    Hi Benoit

    it depends of the institution but we think it's better to let the patron checkin the book before the end of the day no ?

    Yes absolutely. We may have an option "Checkout 1 hour" later, but now the standard behaviour should be checkout X days, for the end of the day.

    @BadrAly Should we open an issue?

    Aboubakr Aly Badr
    @BadrAly
    @pronguen Yes please, an issue to fix this.
    You may also consider this as an optional library parameter. Something like:
    Items due at closing day -> True | False
    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    OK. Thank you.
    Nicolas Prongué
    @pronguen
    rero/rero-ils#417 created, thank you!
    Dubois Laurent
    @itld_solutions_twitter
    Hi,
    it's definitely not the best way but we do a workaround using signal "before_record_update" and connect custom function like :
    def change_loan_end_date(json=None, record=None):
        """Signal before a record is updated."""
    
        """check record type."""
        if record.get('loan_pid', None):
          """fix hour to 23h59."""
          end_date = ciso8601.parse_datetime_as_naive(record.get('end_date'))
          calculated_end_date = end_date.replace(hour=23, minute=59)
          record['end_date'] = calculated_end_date.isoformat()
    Aboubakr Aly Badr
    @BadrAly
    @itld_solutions_twitter Hello Laurent, this is just to let you know that we’re (the dev team) discussing a solution, other than signal before_record_update, for bringing forward the due_dates to the end of the day as requested. We will get back to you soon.
    Aboubakr Aly Badr
    @BadrAly

    Hello @itld_solutions_twitter and @BenoitErken_twitter:

    We have created three pull requests to address the issue of the due date:

    1. invenio-circulation: inveniosoftware/invenio-circulation#117
      changes loan duration from a number of days as int to timedelta (version 1.0.0a16)

    2. rero-ils: rero/rero-ils#436
      upgrades rero-ils to invenio-circulation version 1.0.0a16

    3. rero-ils: rero/rero-ils#440
      adapts the hours of checkouts and renewals due dates to 23:59

    You can enjoy this new feature once these pull requests are merged.

    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    Thank you @BadrAly
    Mana Deweerdt
    @ManaDeweerdt_twitter
    Hi all, we have a question for the renewal functionality.
    It seems for now that when we click on "extend_loan", the renewal is calculated from today's date and not from the due date. Is it correct?
    If it is so, when a user make a renewal 2 weeks before the due date, the new due date will be very short.
    Ex: renewal duration = 14d. Due date = 26/08. Renewal on 21/08 >> New due date = 4/09 (in place of 9/09).
    It would be nice if we could define the number of days before a user can renew the loan. Ex: 4d before the due date.
    Ghost
    @ghost~5b1a499ed73408ce4f9c951e
    [joke] hey @ManaDeweerdt_twitter... don't bother them with circulation trivialities :-))))
    iGor milhit
    @iGormilhit
    @ManaDeweerdt_twitter You're right.
    In config.py, there's a way to set the new due date from the current due date or form the renewal date. You're proposition makes sense, but we have to talk about it with the product owner side of our team... :slight_smile:

    [joke] hey @ManaDeweerdt_twitter... don't bother them with circulation trivialities :-))))

    It seems that we already had discussions about it, quite some time ago... :smiley:

    Mana Deweerdt
    @ManaDeweerdt_twitter
    ;-)
    Renaud Michotte
    @zannkukai
    @pronguen @BadrAly Bonjour Nicolas, Bonjour Ali.
    Ce matin je me suis attelé à la micro tâche #1012 (Clean way to add a default currency). En en reparlant avec Laurent et Benoit, Benoit à soulever un point intéressant.
    Pour le moment, on a défini une currency par défaut dans la configuration générale. Il serait sans doute plus judicieux de définir ce champ dans la description d'une organisation (à priori, toutes les libraries d'une organisation devraient utiliser le même système monétaire). Cela permettrait également à un gestionnaire de pouvoir modifier cette valeur via une interface admin (actuellement la currency par défaut est définie dans le config général de l'application).
    On se trompe ou pas ?
    Si on ne se trompe pas, Il faudrait peut être rajouter cela dans une tâche soit pour ce sprint, soit pour un futur sprint (je pense qu'on pourrait faire cela en interne à l'UCL avec @BadrAly en soutien si nécessaire si biensur il est d'accord).
    Nicolas Prongué
    @pronguen
    Bonjour @zannkukai
    Après un bref échange avec Aly, ta proposition nous semble pertinente. Peut-on modifier la tâche actuelle 1012 dans ce sens?
    Renaud Michotte
    @zannkukai
    @pronguen on peut tout à fait :-) ce sera juste plus long que mes 3 lignes de codes actuelles mais bien plus intéressant pour se mettre dans le bain ;-)
    Aboubakr Aly Badr
    @BadrAly
    @zannkukai Peter, Gianni ou moi serons disponibles en cas de besoin.
    chrswk
    @chrswk

    Hi. We are a RFID provider for Rero/Virtua libraries and have tried to contact the reroils project via the info@ email but never got a reply. We would like to ask regarding:

    1) The integration of our RFID REST-API to checkout/checkin items via RFID in your webapp. We are more than happy to provide you with a devkit including hardware and tags
    2) Your plans for SIP2 or NCIP APIs, which are the de facto standard for self-check/book return, etc. systems to interact with a LMS

    Any change someone can get in contact with me here or via email at devteam@infomedis.ch? Thanks!

    iGor milhit
    @iGormilhit
    Hi @chrswk, thanks for reaching us. Sorry for the absence of answer to your precedent email. We're going to sent to you an email soon. Thanks for your patience!
    chrswk
    @chrswk
    No problem, thanks in advance