Project

General

Profile

Actions

Evolution #77

closed

Default menu / Adding the commune prior to any descriptor would be wise

Added by Yann Le Jeune over 13 years ago. Updated almost 13 years ago.

Status:
Fermé
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
10 January 2011
Due date:
% Done:

100%

Estimated time:
Élément(s):
Difficulté:

Description

peoples refers to a File or Operation first of all with the commune. So, that reference should be added before the reference number so that anyone could easyly find his records.

Examples :

Actually :

2011 - 16 - ZAC de l'horrible site

Becomes :

Le Maisnil - 2011 - 16 - ZAC de l'horrible site

The internal reference (here "ZAC de l'horrible site") should be limited in char so that the menu stays in a easy reading and using way... In most of the case that would be the name of the site or of the project.

The commune should be also presents with the operation default selection process but not with other features (elements, UE, etc.) that have operation in prerequisite.

Actions #1

Updated by Yann Le Jeune over 13 years ago

Most of the time there is only one commune linked to an archeological file or operation, so the commune is usefull as commun descriptor. If there are more than one commune it should be mentionned as "Intercommunal" in the quick default menu (context_processor).

Actions #2

Updated by Anonymous over 13 years ago

  • % Done changed from 0 to 100
  • Status changed from Nouveau to Fermé

Appliqué par commit commit:"f5508ee4d64e321ec6af5437d360c3314bec817f".

Actions #3

Updated by Étienne Loks almost 13 years ago

  • Target version set to 1.0
Actions

Also available in: Atom PDF