contributors are employees, but yes if you are in a country where names change you need to give it a name or id across the changes, in Denmark IIRC we have nicknames for laws, so one law might be called retsplejeloven, and when you get a new version of retsplejeloven even though the actual law name might be changed the nickname remains the same. But if you don't know what the name for something should be you can call it LAWX-1000, 2 years later employee two needs to update the Law, but they don't know it is called LAWX-1000, they would need to look for it and figure out what it was called and update it. One way or another I see a lot of admin work using this method, but I'm also sort of worried am I being overly paranoid about the difficulties the admins will run into.cheers,Bryan RasmussenOn Fri, May 24, 2019 at 11:31 AM Dave Pawson <dave.pawson@gmail.com> wrote:My prime concern would be losing control of the ‘marker’ / ID? Nothing to stop a contributor changing the title - I’d guess they would believe they had total control? If that is going to mess up your system, what’s the cost to you?(I’m ignoring the ‘trouble’ of adding your extra’s to the only bit they are interested in, the document title)HTH--On Fri, 24 May 2019 at 09:22, bryan rasmussen <rasmussen.bryan@gmail.com> wrote:sure, but what I'm actually arguing for (in this project) - as a way to keep admin work low - is to do a similarity search among documents at time of document import, then the admin can choose out of the 5 most similar documents if one is the same, and if not that they can always say no I know this document is the same as document ID X, or just import it as a new document.Otherwise the admins are going to need to do work about figuring out what version they are dealing with and give the document the right 'name' or right id. either way I'd prefer automating that for them as much as possible.but my coworker, who already implemented some stuff before I came on to the project, expects that the admins will put documents into a watched folder on their system, and documents will be named as follows releasedate_correction_titleofdocument.pdf - titleofdocument could be the system document id, but I'm assuming that requires way too much admin work and has chances of being faulty - but it's only an assumption. So I'm hoping others can tell me - yeah I think that is way too problematic, or Bryan you're overthinking it, it won't really be a problem.On Fri, May 24, 2019 at 10:10 AM Dave Pawson <dave.pawson@gmail.com> wrote:Option: Give each document an id / number on entry to your system
and relate that to each document title. Simpler and you have control.
HTH
On Fri, 24 May 2019 at 09:00, bryan rasmussen <rasmussen.bryan@gmail.com> wrote:
>
> Hi,
>
> We are building a system that takes legal documents from many nations and organizations on a particular subject matter in, and needs to be able to version them. A coworker has suggested that when an admin puts in a new document they should name it releasedate_correction_titleofdocument.pdf
>
> however it has been my experience that titleofdocument is not going to cut it for automatically versioning these documents because of course not every country uses the same name between versions of a law. Therefore the admin would have to do work on determining what title of document is - does anyone have any experience on this and how usable would you think the releasedate_correction_titleofdocument.pdf would prove to be in real life?
>
> Thanks,
> Bryan Rasmussen
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.