Giter Site home page Giter Site logo

Comments (6)

franciscave avatar franciscave commented on June 18, 2024

An alternative would be to explain in the note that entity identifiers are always mandatory, but that when they are included in requests to create a new entity they may be ignored by the server.

from bic-lcf.

colinparkeruk avatar colinparkeruk commented on June 18, 2024

Conversely, for the recent sample application for the PlugFest, the identifier was optional when creating a patron. The idea was that this would cater for the situation where new barcoded borrower cards were available at the kiosk and also for when they were not (and the kiosk could then print a receipt containing a barcode to be used temporarily).

from bic-lcf.

anthonywhitford avatar anthonywhitford commented on June 18, 2024

I think the patron and item entities are exceptional cases. Things like
loans and reservations have identifier elements, but I don't think there is
the perception that anything other than the LMS would allocate these. They
are therefore internal unique identifiers defined by the lms. For
consistency we could state this is the case for all identifier elements,
and if there is something like a barcode needed, this could go in a
different element perhaps with a type qualifier since academic libraries
sometimes use the student number as a logical identifier instead of a
barcode. Eg institutional-identifier.
On 14 Jan 2016 21:40, "colinparkeruk" [email protected] wrote:

Conversely, for the recent sample application for the PlugFest, the
identifier was optional when creating a patron. The idea was that this
would cater for the situation where new barcoded borrower cards were
available at the kiosk and also for when they were not (and the kiosk could
then print a receipt containing a barcode to be used temporarily).


Reply to this email directly or view it on GitHub
#18 (comment)
.

from bic-lcf.

franciscave avatar franciscave commented on June 18, 2024

Have we resolved this by my addition of Note [4] in the LCF v1.0.1 spec? If so, I shall add this Note to the XML entity binding spec and we can modify the schemas to make the identifier element non-mandatory (so that it can be used to validate the payload when creating a new entity).

from bic-lcf.

franciscave avatar franciscave commented on June 18, 2024

At the Technical Panel meeting on 28 June it was agreed that the changes are satisfactory. The XML schema should be changed to allow the identifier to be omitted when creating a new instance of the entity.

from bic-lcf.

anthonywhitford avatar anthonywhitford commented on June 18, 2024

The above amendment to the entities with the "identifier" element has been made under issue 20.

from bic-lcf.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.