Skip to content

Releases: OnroerendErfgoed/skosprovider_sqlalchemy

2.1.1

28 Apr 20:08
bc9d9f3
Compare
Choose a tag to compare
  • Fixed an issue with casting ids to string during import. (#104)

2.1.0

30 Mar 19:01
Compare
Choose a tag to compare
  • Minor BC break: Changed the order of parameters to the import_provider
    function and make the conceptscheme argument optional. (#100)

2.0.1

20 Mar 14:23
Compare
Choose a tag to compare
  • Fixed an issue with import_provider still assuming ids are numeric. (#97)

2.0.0

19 Jan 17:59
Compare
Choose a tag to compare
  • Major BC break: Change concept.concept_id from Integer to String to allow
    storing concepts and collections with a non-numeric id. Existing instance will
    need to update their SQL database. Please consult the docs or the README for
    some help in doing so. (#87)
  • Skosprovider_sqlalchemy now depends on SQLAlchemy 1.4 or higher and should be
    compatible with SQLAlchemy 2. Older versions of SQLAlchemy are no longer
    supported. (#90)
  • Refactored the Skosprovider_sqlalchemy constructor to call the super constructor. (#95)
  • Drop support for Python 3.6 and 3.7. Add support for Python 3.11. (#86)
  • Drop pyup support. (#85)

1.0.0

21 Dec 14:05
Compare
Choose a tag to compare
  • drop python 2 support (#80)
  • upgrade requirements (#78)
  • add CITATION.cff

0.6.0

29 Jul 08:01
2289525
Compare
Choose a tag to compare
  • Update to the latest skosprovider version and implement the infer_concept_relations attribute. (#53)
  • Add the ability to query on matches in line with the latest skosprovider version. (#57)
  • Drop the session decorator that was added in 0.4.0 since it did not fix the issue we wanted it to fix and it added a lot of overhead. A provider should now be passed a sqlachemy.orm.session.Session at startup, or a callable that returns such a session. (#64)
  • Improved performance of getting the concept_scheme by caching it. (#71)
  • Make querying a collection with depth=all possible. Before the provider would only provide the direct members of a collection. (#76)
  • Drop support for Python 3.4 and 3.5. Add support for Python 3.7 and 3.8. This is also the last version to support Python 2. (#62)

0.5.2

13 Nov 22:43
70bf1e1
Compare
Choose a tag to compare
  • Update a lot of dependencies.
  • Add str implementations to the model classes. (#43)

0.5.1

07 Dec 17:58
0.5.1
Compare
Choose a tag to compare
  • Catch linking errors when importing a provider and turn them into log warning. By linking errors we mean cases where one concept has a relation to a non-existing other concept. (#25)
  • Allow building as wheel.

0.5.0

11 Aug 12:52
0.5.0
Compare
Choose a tag to compare
  • Update to skosprovider 0.6.0
  • Minor BC break: A skosprovider_sqlalchemy.models.Language that gets cast to a string, now returns the language's ID (the IANA language code),as opposed to the language's description it would previously return.
  • Minor BC break: The URI attribute has been made required for a skosprovider_sqlalchemy.models.ConceptScheme. Before it was optional, but it probably would have caused problems with skosprovider anyway.
  • Due to the update to skosprovider 0.6.0, a new field markup, was added to a skosprovider_sqlalchemy.models.Note. When upgrading from a previous version of skosprovider_sqlalchemy, any databases created in that previous verions will need to be updated as well. Please add a field called markup to the note table.
  • Inline with the skosprovider 0.6.0 update, a languages attribute was added to skosprovider_sqlalchemy.models.ConceptScheme. When upgrading from a previous version of skosprovider_sqlalchemy, any databases created with that previous verions will need to be updated as well. Please add a table called conceptscheme_language with fields conceptscheme_id and language_id. (#18)
  • To comply with the skosprovider 0.6.0 update, the sources attribute was added to skosprovider_sqlalchemy.models.Conceptscheme, skosprovider_sqlalchemy.models.Concept and skosprovider_sqlalchemy.models.Collection. When upgrading from a previous version of skosprovider_sqlalchemy, any databases created with that previous verions will need to be updated as well. Please add a table source with fields id, citation and markup, a table concept_source with fields concept_id and source_id and a table conceptscheme_source with fields conceptscheme_id and source_id.
  • All methodes that return a list have been modified in line with skosprovider 0.6.0 to support sorting. Sorting is possible on id, uri, label and sortlabel. The last two are language dependent. The sortlabel allows custom sorting of concepts. This can be used to eg. sort concepts representing chronological periods in chronological in stead of alphabetical order. (#20)
  • To comply with the skosprovider 0.6.0 update, the deprecated skosprovider_sqlalchemy.providers.SQLAlchemyProvider.expand_conceptwas removed.
  • When importing a provider, check if the languages that are being used in the provider are already in our database. If not, validate them and add them to the database. In the past the entire import would fail if not all languages had previously been added to the database. (#14)
  • When importing a provider, try to import as much information as possible about the concept_scheme that's attached to the provider. (#19)
  • When querying for indvidual an conceptscheme or concept, use joinedload to reduce the number of queries needed to collect everything. (#15)
  • Deprecated the :func:skosprovider_sqlalchemy.models.label function. Please use skosprovider.skos.label from now once, since this function can now operate on both skosprovider.skos.Label and skosprovider_sqlalchemy.models.Label instances. This was the reason for the BC break in this release.

0.4.2

02 Mar 21:23
Compare
Choose a tag to compare
  • Make README work better on pypi.
  • Fix a further problem with the length of language identifiers. Previous fix in 0.3.0 only fixed the length of the identifiers in the languages table, but not in the links from the labels and the notes to the language table. [@BartSaelen]
  • Added some documentation about setting up a database.