bold type for parent folder

[jodevelops]

Parent folder should be bold, if there are access/ edit rights for any of its subfolders. The red folder "samples" should be displayed in bold letters, so that a user can see it contains folders, that can be accessed.

[jensopetersen]

The question is what to do if you have a situation like the following (common, I would say):

The folder hierarchy

A > B > C

A, B, and C also contain documents

You have write rights on some documents in C. Should A, B and C then all show up bold?

[jodevelops]

1. Will rights be managed on document-level? I thought this will be handled on a collection's (=folders) level.
2. And: can there be folders AND records on the same level? I thought ALL records had to be organized in (sub-) folders, so that there is no such situation where a folder (collection) can have both, records AND other (sub-) folders.

In both cases however, my answer would be yes. Or more generally: rights on a lower level SHOULD affect the appearance of the labels (or even icons) on a higher level(s).

M.A. introduced a suggestion for a third differentiation some time ago: Make all folder-labels that DO NOT IMMEDIATELY contain the actual records _bold AND italics_, instead of just bold.

Three differentiations:

• No rights in none of the folder's content (including subfolders) = NORMAL TEXT
• Some rights in one ore more of the folder's subfolders = _BOLD ITALICS_
• Full rights on all of the folder's own contents = BOLD

In the initial example (screenshot, see above!), the user will know for sure, that there are FULL write rights on all of "VRA Record Samples'" contents. That's very valuable information, we think.

[jensopetersen]

@1. Document rights are at present handled by collection rights. Are we ruling out setting rights on individual documents? @2. Yes. The typical VRA scenario involves a folder containing 1) work records and 2) a subfolder containing image records and images. This is not very smart, in my opinion: work records, image records and images should be in separate collections under the project collection.

[withanage]

For the 2 First implementation phase it was needed as a separate folder so that the images folders can be separated and blended away. Therefore the implementation was like that. That can be changed in upload script. But have to be taken care in search interface. On Dec 10, 2013 9:31 AM, "Jens Østergaard Petersen" < notifications@github.com> wrote:

@1 https://github.com/1. Document rights are at present handled by collection rights. Are we ruling out setting rights on individual documents? @2 https://github.com/2. Yes. The typical VRA scenario involves a folder containing 1) work records and 2) a subfolder containing image records and images. This is not very smart, in my opinion: work records, image records and images should be in separate collections under the project collection.

— Reply to this email directly or view it on GitHubhttps://github.com/eXist-db/tamboti/issues/72#issuecomment-30207444 .

[jensopetersen]

I don't think having the three in separate collections would create problems for search, since everything goes by UUID anyway.

[MatthiasArnold]

the separation of work and image records is still needed.

vra works may appear without image records.

although by definition standalone vra image records are not allowed, we need to provide a means to upload image records individually -and be stored as that, while "in transition"- before they get assigned to one (or more) works.

in addition, we will have to think about the vra collection records, because they may not only contain settings that will be passed down to work/image reords (e.g. languageOfCataloging) but also a description of the collection as such.

will there also be collection records in mods? should we provide collection records for all tamboti collections to be able to create a list of collections, like teasers, as is often the case in larger institutions? cf. http://www.loc.gov/pictures/collections/

[jensopetersen]

There is nothing similar to a VRA collection record in MODS. A modsCollection element is just a wrapper around a number of mods records and it does not contain any collection metadata.

The "teaser" is there already, in the tab "Tamboti Collections".

I don't think we disagree about the various VRA records - I just want them (perhaps except the collection records) to be stored in separate collections under the same project collection, to avoid having records and collections at the same level.

[jodevelops]

I think we will have to split this up into at least 4 or 5 different (related) issues / feature requests.