Search results
Jump to navigation
Jump to search
Create the page "Feature requirements" on this wiki! See also the search results found.
- ===Requirements Analysis=== *[[DROID,_JHOVE,_NLNZ_Metadata_Extractor|Ingest tools feature comparison]]1 KB (126 words) - 13:21, 3 July 2015
- = Requirements = [[Category:Feature requirements]]297 bytes (39 words) - 14:44, 23 March 2017
- -capture requirements in a feature file -how can asyncronous processing in the Storage Service make this proposed feature more efficient or easier537 bytes (84 words) - 16:10, 23 August 2017
- -capture requirements in a feature file -how can asyncronous processing in the Storage Service make this proposed feature more efficient or easier537 bytes (84 words) - 16:07, 23 August 2017
- [[Category:Feature requirements]] == Requirements ==1 KB (175 words) - 17:14, 11 February 2020
- [[Category:Feature requirements]] == Requirements ==904 bytes (116 words) - 17:17, 11 February 2020
- [[Main Page]] > [[Development]] > [[Requirements]] > Object-level PREMIS rights import [[Category:Feature requirements]]3 KB (459 words) - 17:27, 11 February 2020
- This page documents preliminary requirements for DIP upload to DSpace. [[Category:Feature requirements]]2 KB (262 words) - 17:17, 11 February 2020
- [[Documentation]] > [[Requirements]] > Processing report requirements [[Category:Feature requirements]]2 KB (242 words) - 17:23, 11 February 2020
- [[Main Page]] > [[Documentation]] > [[Requirements]] > Fixity checking and reporting This wiki page describes requirements for gathering fixity check information from the [https://github.com/artefac2 KB (274 words) - 17:24, 11 February 2020
- [[Category:Feature requirements]] == Requirements ==1 KB (214 words) - 17:17, 11 February 2020
- [[Category:Feature requirements]] == Requirements ==3 KB (413 words) - 17:22, 11 February 2020
- ...stitute) AIP DC and Rights MD Re-ingest [[AIP_re-ingest|Full AIP re-ingest requirements]] ** note that this work is only part of the entire AIP re-ingest feature, the rest is not yet sponsored2 KB (217 words) - 17:51, 9 June 2016
- ==Feature description== ==Requirements==5 KB (560 words) - 16:41, 11 February 2020
- [[Documentation]] > [[Requirements]] > Metrics requirements [[Category:Feature requirements]]3 KB (508 words) - 17:26, 11 February 2020
- [[Category:Feature requirements]]1 KB (187 words) - 14:46, 23 March 2017
- *Evelyn and Mike C looked at TRIM DIP upload requirements together and Evelyn made a sample DIP *Justin working on upload to Archivists Toolkit feature for client #1885; testing against a copy of the client's AT db2 KB (263 words) - 16:48, 20 February 2013
- [[Category:Feature requirements]] ...o generate access derivatives after the AIP creation workflow is a desired feature, which could be supported with enhancements to the Format Policy Registry.5 KB (774 words) - 09:06, 29 August 2017
- [[Documentation]] > [[Requirements]] > Format identification requirements [[Category:Feature requirements]]4 KB (636 words) - 17:25, 11 February 2020
- [[Main Page]] > [[Development]] > [[Requirements]] > Archivists' Toolkit integration This feature will re-format a DIP for import into Archivists' Toolkit.5 KB (750 words) - 17:15, 11 February 2020
- [[Category:Feature requirements]] ====Transfer indexing requirements 0.9 and beyond====4 KB (580 words) - 17:28, 11 February 2020
- ...egory:Development documentation|Development documentation]] > File Browser Requirements This page describes requirements for moving all Archivematica interface to the web dashboard, including file4 KB (606 words) - 17:23, 11 February 2020
- ...velopment documentation|Development documentation]] > Manual normalization requirements and testing procedures [[Category:Feature requirements]]8 KB (1,189 words) - 17:25, 11 February 2020
- Page for requirements gathering for integration of [https://mediaarea.net/MediaConch/ Media Conch [[Category:Feature requirements]]14 KB (1,625 words) - 17:25, 11 February 2020
- [[Main Page]] > [[Requirements]] > AIP re-ingest This page documents requirements for retrieving an Archivematica AIP from archival storage and re-ingesting4 KB (553 words) - 17:14, 11 February 2020
- [[Main Page]] > [[Development]] > [[Requirements]] > Appraisal and Arrangement Tab [[Category:Feature requirements]]8 KB (1,191 words) - 17:15, 11 February 2020
- ...y:Development documentation|Development documentation]] > Transfer backlog requirements [[Category:Feature requirements]]8 KB (1,057 words) - 17:27, 11 February 2020
- [[Category:Feature requirements]] Adding a way to perform work asynchronously is an important feature, probably a requirement before a 1.0.0 version of the Storage Service can b4 KB (685 words) - 10:19, 16 August 2017
- .... 24, code freeze for Nov. 7, release for Nov. 21. We'll have an in office feature freeze/release schedule meeting on Tue Oct 18 at 11:00 am. Evelyn will tack (10:46:08 AM) berwin22: I don't see an archivematica feature freeze in the calendar14 KB (1,999 words) - 13:17, 12 October 2011
- [[Category:Feature requirements]] ...st from FTK Imager, but later from other tools like Guymager (see metadata requirements below)11 KB (1,600 words) - 17:16, 11 February 2020
- <div class="description">This page proposes a new feature and reviews design options</div> <div class="description">This page describes a feature that's in development</div>14 KB (1,994 words) - 16:43, 11 February 2020
- ...equirements for this, it's actually quite complex. It will be a nice 0.7.1 feature. (7:45:54 PM) epmclellan: Joseph and I are working on the requirements for this, it's actually quite complex9 KB (1,367 words) - 15:25, 21 September 2011
- ...rompts are given when creating a new user if the password doesn't meet the requirements. This feature was '''sponsored''' by the City of Winnipeg Archives. Thank you!6 KB (832 words) - 14:11, 25 February 2022
- [[Main Page]] > [[Development]] > [[Requirements]] > [[ArchivesSpace_integration|ArchivesSpace integration]] > SAA 2015 demo This functionality will mirror the current arrangement feature in Archivematica's Ingest tab. In this case, however, you will be able to l8 KB (1,210 words) - 10:23, 27 August 2015
- ...we can standardize on maildir ingest for 0.9 that will be a really useful feature ...t 9.0 but will need to work over next two months on identifying strategy / requirements10 KB (1,519 words) - 13:15, 16 May 2012
- [[Category:Feature requirements]] * This integration is currently considered a beta feature.9 KB (1,286 words) - 14:49, 23 March 2017
- (10:41:01) peterVG: pretty sophisticated feature ...e that these were taken care of in code updates and not new install/config requirements that Austin needs to be aware of when building the VMs9 KB (1,347 words) - 14:54, 4 January 2012
- [[Main Page]] > [[Development]] > [[Requirements]] > ArchivesSpace integration [[Category:Feature requirements]]10 KB (1,103 words) - 17:15, 11 February 2020
- [[Category:Feature requirements]] ==Functional Requirements==12 KB (1,809 words) - 14:48, 23 March 2017
- [[Documentation]] > [[Requirements]] > Format policy registry requirements ...olicy or the selected Command format policy default for normalization. See Feature #450313 KB (1,898 words) - 16:51, 11 February 2020
- [[Main Page]] > [[Documentation]] > [[Requirements]] > Dataverse This page sets out the requirements and designs for integration with [http://dataverse.org Dataverse]. As of Ar38 KB (5,317 words) - 10:28, 8 April 2020
- [[Main Page]] > [[Development]] > [[Requirements]] > [[Appraisal Arrangement tab]] > Archivematica to ArchivesSpace Workflow Now the user must locate the transfer in the backlog. The tags feature can also be used to identify information relevant for appraisal and arrange5 KB (817 words) - 18:37, 13 April 2016
- [[Category:Feature requirements]]11 KB (1,277 words) - 14:50, 23 March 2017
- [[Category:Feature requirements]]5 KB (740 words) - 17:26, 11 February 2020
- If your transfer is an email transfer, this feature is still under development, please see [[Email]] ...ctionality in the web browser. See [File_Browser_Requirements|File browser requirements - Create SIP] and [Transfer_and_SIP_creation|Transfer and SIP creation work6 KB (860 words) - 15:37, 24 April 2013
- Previously, the ElasticSearch index feature could be disabled globally as a scalability measure since indexing consumes ...tica (i.e. normalization reports, failure reports) to comply with local IT requirements.19 KB (2,494 words) - 16:34, 21 January 2019
- <div class="description">This page proposes a new feature and reviews design options</div> <div class="description">This page describes a feature that's in development</div>21 KB (3,008 words) - 17:03, 11 February 2020
- This page documents ingest of TRIM exports based on requirements for VanDocs ingest at City of Vancouver Archives. [[Category:Feature requirements]]9 KB (1,274 words) - 17:28, 11 February 2020
- * 0.9 Feature freeze is today, a meeting yesterday clarified the roadmap * Evelyn updated maildir processing requirements at https://www.archivematica.org/wiki/Email_preservation#Archivematica_0.9_11 KB (1,558 words) - 13:12, 30 May 2012
- [[Main Page]] > [[Documentation]] > [[Requirements]] > Sword API [[Category:Feature requirements]]16 KB (2,397 words) - 17:27, 11 February 2020
- If your transfer is an email transfer, this feature is still under development, please see [[Email]] ...ctionality in the web browser. See [File_Browser_Requirements|File browser requirements - Create SIP] and [Transfer_and_SIP_creation|Transfer and SIP creation work8 KB (1,264 words) - 18:56, 30 September 2013
- [[Category:Feature requirements]] *Minimal development requirements, just new metadata field for identifier added to transfer tab, correspondin18 KB (2,649 words) - 17:16, 11 February 2020
- [[Category:Feature requirements]]46 KB (5,043 words) - 17:25, 11 February 2020